Erik Johnston a6ea1a957e Don't pull event from DB when handling replication traffic. (#8669) ... I was trying to make it so that we didn't have to start a background task when handling RDATA, but that is a bigger job (due to all the code in `generic_worker`). However I still think not pulling the event from the DB may help reduce some DB usage due to replication, even if most workers will simply go and pull that event from the DB later anyway. Co-authored-by: Patrick Cloke <clokep@users.noreply.github.com>		2020-10-28 12:11:45 +00:00
..
streams	Don't pull event from DB when handling replication traffic. (#8669)	2020-10-28 12:11:45 +00:00
__init__.py	Fix some spelling mistakes / typos. (#7811)	2020-07-09 09:52:58 -04:00
client.py	Don't pull event from DB when handling replication traffic. (#8669)	2020-10-28 12:11:45 +00:00
commands.py	Make event persisters periodically announce position over replication. (#8499)	2020-10-12 15:51:41 +01:00
handler.py	Make event persisters periodically announce position over replication. (#8499)	2020-10-12 15:51:41 +01:00
protocol.py	Enable mypy checking for unreachable code and fix instances. (#8432)	2020-10-01 08:09:18 -04:00
redis.py	Start fewer opentracing spans (#8640)	2020-10-26 09:30:19 +00:00
resource.py	Don't unnecessarily start bg process in replication sending loop. (#8670)	2020-10-27 17:37:08 +00:00