summaryrefslogtreecommitdiff
path: root/doc/administration/geo
diff options
context:
space:
mode:
authorIan Baum <ibaum@gitlab.com>2019-07-15 13:49:32 +0000
committerAchilleas Pipinellis <axil@gitlab.com>2019-07-15 13:49:32 +0000
commita45c5e185879b390345ac363e1e26def00dd1a3f (patch)
tree6111b9272649804184220a0aaaad6105a044f387 /doc/administration/geo
parent29662cdce3b7a4728ecd98c8e31c99d97473e483 (diff)
downloadgitlab-ce-a45c5e185879b390345ac363e1e26def00dd1a3f.tar.gz
Add note to GEO documentation about database upgrade
* Point to the omnibus documentation for how to upgrade the cluster * Document how to disable the upgrade procedure
Diffstat (limited to 'doc/administration/geo')
-rw-r--r--doc/administration/geo/replication/updating_the_geo_nodes.md10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/administration/geo/replication/updating_the_geo_nodes.md b/doc/administration/geo/replication/updating_the_geo_nodes.md
index c27f6c78455..166ee94eca4 100644
--- a/doc/administration/geo/replication/updating_the_geo_nodes.md
+++ b/doc/administration/geo/replication/updating_the_geo_nodes.md
@@ -14,6 +14,16 @@ all you need to do is update GitLab itself:
the tracking database is enabled.
1. [Test](#check-status-after-updating) **primary** and **secondary** nodes, and check version in each.
+## Upgrading to GitLab 12.1
+
+By default, GitLab 12.1 will attempt to automatically upgrade the embedded PostgreSQL server to 10.7 from 9.6. Please see [the omnibus documentation](https://docs.gitlab.com/omnibus/settings/database.html#upgrading-a-geo-instance) for the recommended procedure.
+
+This can be temporarily disabled by running the following before ugprading:
+
+```sh
+sudo touch /etc/gitlab/disable-postgresql-upgrade
+```
+
## Upgrading to GitLab 10.8
Before 10.8, broadcast messages would not propagate without flushing the cache on the **secondary** nodes. This has been fixed in 10.8, but requires one last cache flush on each **secondary** node: