From 760ea7ac5cc6f51243a6b35471398465cfd5cf98 Mon Sep 17 00:00:00 2001 From: erikjohnston Date: Wed, 29 May 2024 11:05:50 +0000 Subject: deploy: 967b6948b0d738bc685d433d44e82631fd2ad232 --- develop/postgres.html | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) (limited to 'develop/postgres.html') diff --git a/develop/postgres.html b/develop/postgres.html index 15c2eaada8..96fbff6340 100644 --- a/develop/postgres.html +++ b/develop/postgres.html @@ -349,12 +349,11 @@ new line, it is inserted before:

host    all         all             ::1/128     ident
 

Fixing incorrect COLLATE or CTYPE

-

Synapse will refuse to set up a new database if it has the wrong values of -COLLATE and CTYPE set. Synapse will also refuse to start an existing database with incorrect values -of COLLATE and CTYPE unless the config flag allow_unsafe_locale, found in the -database section of the config, is set to true. Using different locales can cause issues if the locale library is updated from -underneath the database, or if a different version of the locale is used on any -replicas.

+

Synapse will refuse to start when using a database with incorrect values of +COLLATE and CTYPE unless the config flag allow_unsafe_locale, found in the +database section of the config, is set to true. Using different locales can +cause issues if the locale library is updated from underneath the database, or +if a different version of the locale is used on any replicas.

If you have a database with an unsafe locale, the safest way to fix the issue is to dump the database and recreate it with the correct locale parameter (as shown above). It is also possible to change the parameters on a live database and run a REINDEX on the entire database, -- cgit 1.5.1