summary refs log tree commit diff
path: root/latest/postgres.html
diff options
context:
space:
mode:
authorerikjohnston <erikjohnston@users.noreply.github.com>2023-09-26 16:01:35 +0000
committererikjohnston <erikjohnston@users.noreply.github.com>2023-09-26 16:01:35 +0000
commit2a48d0838b46963b134b4351d4da0dd352cbd8bf (patch)
tree9f615b3044851520d090d8d6839c2c46ab7997ab /latest/postgres.html
parentdeploy: ec1c709440d99b0d8042b669e17c899cd6fd8b84 (diff)
downloadsynapse-2a48d0838b46963b134b4351d4da0dd352cbd8bf.tar.xz
deploy: 88ba67eb91215a708f321e16559fe3c2c0d0a407
Diffstat (limited to 'latest/postgres.html')
-rw-r--r--latest/postgres.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/latest/postgres.html b/latest/postgres.html

index f3e98fda6e..4c487267ab 100644 --- a/latest/postgres.html +++ b/latest/postgres.html
@@ -342,7 +342,7 @@ of <code>COLLATE</code> and <code>CTYPE</code> unless the config flag <code>allo <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 databse with an unsafe locale, the safest way to fix the issue is to dump the database and recreate it with +<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, however extreme care must be taken to avoid database corruption.</p>