Skip to content
Snippets Groups Projects
Commit 02c0dc2f authored by Evan Read's avatar Evan Read
Browse files

Merge branch 'docs_geo_pgsql_upgrades' into 'master'

Add caveat to known issue with Geo and PostgreSQL upgrades

Closes #8947

See merge request https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/8219



Merged-by: default avatarEvan Read <eread@gitlab.com>
Approved-by: default avatarMichael Kozono <mkozono@gitlab.com>
Approved-by: default avatarEvan Read <eread@gitlab.com>
Reviewed-by: default avatarEvan Read <eread@gitlab.com>
Co-authored-by: default avatarMichael Hofer <michael.hofer@adfinis.com>
parents 0bc0030c d6e5b11d
No related branches found
No related tags found
No related merge requests found
......@@ -100,4 +100,8 @@
## Known issues
Geo uses streaming replication, which requires that the entire secondary database be resynced after a major PostgreSQL upgrade. This can cause hours or days of downtime, and as such, we do not recommend auto upgrades for Geo customers. Starting in 12.10, automatic PostgreSQL upgrades are disabled if Geo is detected.
Geo uses streaming replication, which resynchronizes the entire secondary database after a major PostgreSQL upgrade. Because this resynchronization can cause hours or days
of downtime, you should not do automatic upgrades if you use Geo.
Automatic PostgreSQL upgrades are disabled in some, but not all, cases when Geo is also configured. Therefore you should
[opt out of automatic PostgreSQL upgrades](../settings/database.md#opt-out-of-automatic-postgresql-upgrades) and only perform PostgreSQL upgrades deliberately.
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment