mirror of
https://mau.dev/maunium/synapse.git
synced 2024-08-24 19:25:57 +00:00
Re-run rejected metadata background update. (#9503)
It landed in schema version 58 after 59 had been created, causing some servers to not run it. The main effect of was that not all rooms had their chain cover calculated correctly. After the BG updates complete the chain covers will get fixed when a new state event in the affected rooms is received.
This commit is contained in:
parent
16108c579d
commit
7f5d753d06
1
changelog.d/9503.bugfix
Normal file
1
changelog.d/9503.bugfix
Normal file
@ -0,0 +1 @@
|
|||||||
|
Fix missing chain cover index due to a schema delta not being applied correctly. Only affected servers that ran development versions.
|
@ -13,5 +13,14 @@
|
|||||||
* limitations under the License.
|
* limitations under the License.
|
||||||
*/
|
*/
|
||||||
|
|
||||||
|
-- This originally was in 58/, but landed after 59/ was created, and so some
|
||||||
|
-- servers running develop didn't run this delta. Running it again should be
|
||||||
|
-- safe.
|
||||||
|
--
|
||||||
|
-- We first delete any in progress `rejected_events_metadata` background update,
|
||||||
|
-- to ensure that we don't conflict when trying to insert the new one. (We could
|
||||||
|
-- alternatively do an ON CONFLICT DO NOTHING, but that syntax isn't supported
|
||||||
|
-- by older SQLite versions. Plus, this should be a rare case).
|
||||||
|
DELETE FROM background_updates WHERE update_name = 'rejected_events_metadata';
|
||||||
INSERT INTO background_updates (ordering, update_name, progress_json) VALUES
|
INSERT INTO background_updates (ordering, update_name, progress_json) VALUES
|
||||||
(5828, 'rejected_events_metadata', '{}');
|
(5828, 'rejected_events_metadata', '{}');
|
Loading…
Reference in New Issue
Block a user