Erik Johnston b1433bf231 Don't table scan events on worker startup (#8419) ... * Fix table scan of events on worker startup. This happened because we assumed "new" writers had an initial stream position of 0, so the replication code tried to fetch all events written by the instance between 0 and the current position. Instead, set the initial position of new writers to the current persisted up to position, on the assumption that new writers won't have written anything before that point. * Consider old writers coming back as "new". Otherwise we'd try and fetch entries between the old stale token and the current position, even though it won't have written any rows. Co-authored-by: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com> Co-authored-by: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com>		2020-09-29 16:42:19 +01:00
..
api
app
appservice
config
crypto
events
federation
handlers
http
logging
module_api
push
replication
rest
scripts
server_notices
state
storage	Don't table scan events on worker startup (#8419)	2020-09-29 16:42:19 +01:00
test_utils
util
__init__.py
server.py
test_distributor.py
test_event_auth.py
test_federation.py
test_mau.py
test_metrics.py
test_phone_home.py
test_preview.py
test_server.py
test_state.py	Simplify super() calls to Python 3 syntax. (#8344)	2020-09-18 09:56:44 -04:00
test_terms_auth.py
test_test_utils.py
test_types.py
test_visibility.py
unittest.py
utils.py