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
..
http	Fix message duplication if something goes wrong after persisting the event (#8476)	2020-10-13 12:07:56 +01:00
slave	Replace DeferredCache with LruCache where possible (#8563)	2020-10-19 12:20:29 +01:00
tcp	Don't pull event from DB when handling replication traffic. (#8669)	2020-10-28 12:11:45 +00:00
__init__.py	Add a /replication API for extracting the updates that happened on	2016-03-01 14:49:41 +00:00