From afc7b0d320c77dd9c93876e39f64e679e9d4bd37 Mon Sep 17 00:00:00 2001 From: Alvin Gounder <agounder@gitlab.com> Date: Thu, 1 Feb 2024 10:10:08 +0000 Subject: [PATCH] Clarify note to include both DB deployment types --- doc/administration/geo/replication/upgrading_the_geo_sites.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/doc/administration/geo/replication/upgrading_the_geo_sites.md b/doc/administration/geo/replication/upgrading_the_geo_sites.md index de30b85f4a7d2..b9e9fac85addc 100644 --- a/doc/administration/geo/replication/upgrading_the_geo_sites.md +++ b/doc/administration/geo/replication/upgrading_the_geo_sites.md @@ -15,7 +15,8 @@ Read these sections carefully before updating your Geo sites. Not following version-specific upgrade steps may result in unexpected downtime. If you have any specific questions, [contact Support](https://about.gitlab.com/support/#contact-support). A database major version upgrade requires [re-initializing the PostgreSQL replication](https://docs.gitlab.com/omnibus/settings/database.html#upgrading-a-geo-instance) -to Geo secondaries. This may result in a larger than expected downtime. +to Geo secondaries. This applies to both Linux-packaged and externally-managed databases. +This may result in a larger than expected downtime. Upgrading Geo sites involves performing: -- GitLab