| Commit message (Collapse) | Author | Files | Lines |
|
We're up to schema v47 on develop now, so this will have to go in there to have
an effect.
This might cause an error if somebody has already run it in the v46 guise, and
runs it again in the v47 guise, because it will cause a duplicate entry in the
bbackground_updates table. On the other hand, the entry is removed once it is
complete, and it is unlikely that anyone other than matrix.org has run it on
v46. The update itself is harmless to re-run because it deliberately copes with
the index already existing.
|
|
|
|
... to avoid locking the table for too long
|
|
Add a flag which makes the purger delete local events
|
|
it was a bit of a non-sequitur there
|
|
this thing takes ages and the only sign of any progress is the logs, so having
some logs is useful.
|
|
(beacause it deletes more than state)
|
|
|
|
The intention was for the check to be called as early as possible in the
request, but actually was called just before the main ratelimit check,
so was fairly pointless.
|
|
|
|
|
|
* Split state group persist into seperate storage func
* Add per database engine code for state group id gen
* Move store_state_group to StateReadStore
This allows other workers to use it, and so resolve state.
* Hook up store_state_group
* Fix tests
* Rename _store_mult_state_groups_txn
* Rename StateGroupReadStore
* Remove redundant _have_persisted_state_group_txn
* Update comments
* Comment compute_event_context
* Set start val for state_group_id_seq
... otherwise we try to recreate old state groups
* Update comments
* Don't store state for outliers
* Update comment
* Update docstring as state groups are ints
|
|
we already have the state from _get_new_state_after_events, so returning it
from _calculate_state_delta is just confusing.
|
|
we can reuse the same code as is used for event insert, for doing the
background index population.
|
|
|
|
|
|
|
|
... as a precursor to making event storing and doing the bg update share some
code.
|
|
|
|
|
|
|
|
we can reuse the same code as is used for event insert, for doing the
background index population.
|
|
Add some comments and improve exception handling when twiddling work_mem for
the search update
|
|
... as a precursor to making event storing and doing the bg update share some
code.
|
|
People may have queued updates for this, so we can't just delete it.
|
|
avoid failing with an exception if the remote server doesn't give us a
Content-Type header.
Also, clean up the exception handling a bit.
|
|
|
|
Fix a couple of errors in docstrings
|
|
The return type was a complete lie, so fix it
|
|
We extract the storage-independent bits of the state group resolution out to a
separate functiom, and stick it in a new handler, in preparation for its use
from the storage layer.
|