summary refs log tree commit diff
path: root/docs/postgres.md
diff options
context:
space:
mode:
authorErik Johnston <erikj@element.io>2024-06-14 16:40:29 +0100
committerGitHub <noreply@github.com>2024-06-14 16:40:29 +0100
commita3cb24475577c31fa2c16a26fccddb76daf2f6ae (patch)
tree276857cea7909cee15eed5a5067423517b5da0bc /docs/postgres.md
parentCHANGES.md: s/OTKs/one-time-keys/ (diff)
downloadsynapse-a3cb24475577c31fa2c16a26fccddb76daf2f6ae.tar.xz
Automatically apply SQL for inconsistent sequence (#17305)
Rather than forcing the server operator to apply the SQL manually.

This should be safe, as there should be only one writer for these
sequences.
Diffstat (limited to 'docs/postgres.md')
-rw-r--r--docs/postgres.md10
1 files changed, 0 insertions, 10 deletions
diff --git a/docs/postgres.md b/docs/postgres.md
index 4b2ba38275..d06f0cda10 100644
--- a/docs/postgres.md
+++ b/docs/postgres.md
@@ -255,13 +255,3 @@ however extreme care must be taken to avoid database corruption.
 
 Note that the above may fail with an error about duplicate rows if corruption
 has already occurred, and such duplicate rows will need to be manually removed.
-
-### Fixing inconsistent sequences error
-
-Synapse uses Postgres sequences to generate IDs for various tables. A sequence
-and associated table can get out of sync if, for example, Synapse has been
-downgraded and then upgraded again.
-
-To fix the issue shut down Synapse (including any and all workers) and run the
-SQL command included in the error message. Once done Synapse should start
-successfully.