deploy: 967b6948b0d738bc685d433d44e82631fd2ad232

1 files changed, 5 insertions, 6 deletions

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:</p>
 <pre><code>host    all         all             ::1/128     ident
 </code></pre>
 <h3 id="fixing-incorrect-collate-or-ctype"><a class="header" href="#fixing-incorrect-collate-or-ctype">Fixing incorrect <code>COLLATE</code> or <code>CTYPE</code></a></h3>
-<p>Synapse will refuse to set up a new database if it has the wrong values of
-<code>COLLATE</code> and <code>CTYPE</code> set. Synapse will also refuse to start an existing database with incorrect values
-of <code>COLLATE</code> and <code>CTYPE</code> unless the config flag <code>allow_unsafe_locale</code>, found in the 
-<code>database</code> 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.</p>
+<p>Synapse will refuse to start when using a database with incorrect values of
+<code>COLLATE</code> and <code>CTYPE</code> unless the config flag <code>allow_unsafe_locale</code>, found in the
+<code>database</code> 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.</p>
 <p>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 <code>REINDEX</code> on the entire database,