Only start censor background job after indices are created

This commit is contained in:
Erik Johnston 2019-12-10 11:39:31 +00:00
parent 52fe9788bc
commit cc5f6eb608
2 changed files with 9 additions and 2 deletions

View File

@ -1053,6 +1053,13 @@ class EventsStore(
if self.hs.config.redaction_retention_period is None: if self.hs.config.redaction_retention_period is None:
return return
if self.db.updates.has_completed_background_update(
"redactions_have_censored_ts_idx"
):
# We don't want to run this until the appropriate index has been
# created.
return
before_ts = self._clock.time_msec() - self.hs.config.redaction_retention_period before_ts = self._clock.time_msec() - self.hs.config.redaction_retention_period
# We fetch all redactions that: # We fetch all redactions that:

View File

@ -18,5 +18,5 @@ ALTER TABLE redactions ADD COLUMN received_ts BIGINT;
INSERT INTO background_updates (update_name, progress_json) VALUES INSERT INTO background_updates (update_name, progress_json) VALUES
('redactions_received_ts', '{}'); ('redactions_received_ts', '{}');
INSERT INTO background_updates (update_name, progress_json) VALUES INSERT INTO background_updates (update_name, progress_json, depends_on) VALUES
('redactions_have_censored_ts_idx', '{}'); ('redactions_have_censored_ts_idx', '{}', 'redactions_have_censored_idx');