summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMarcel Amirault <ravlen@gmail.com>2019-06-06 02:26:50 +0000
committerEvan Read <eread@gitlab.com>2019-06-06 02:26:50 +0000
commit3376af6bd9b25b6bba9669a0c3edc878a954a54d (patch)
tree1b953f2f17e3c7ad73eda0849249504b00529730
parentab095deae2107b178e5373ce3097631d13413e6f (diff)
downloadgitlab-ce-3376af6bd9b25b6bba9669a0c3edc878a954a54d.tar.gz
Docs: Update anchor to more recent section in geo db doc
-rw-r--r--doc/administration/geo/replication/database.md3
1 files changed, 1 insertions, 2 deletions
diff --git a/doc/administration/geo/replication/database.md b/doc/administration/geo/replication/database.md
index c0cdea216cb..1e5a56c3f4e 100644
--- a/doc/administration/geo/replication/database.md
+++ b/doc/administration/geo/replication/database.md
@@ -445,8 +445,7 @@ The replication process is now complete.
PostgreSQL connections. We recommend using PGBouncer if you use GitLab in a
high-availability configuration with a cluster of nodes supporting a Geo
**primary** node and another cluster of nodes supporting a Geo **secondary** node. For more
-information, see the [Omnibus HA](../../high_availability/database.md#configure-using-omnibus)
-documentation.
+information, see [High Availability with GitLab Omnibus](../../high_availability/database.md#high-availability-with-gitlab-omnibus-premium-only).
For a Geo **secondary** node to work properly with PGBouncer in front of the database,
it will need a separate read-only user to make [PostgreSQL FDW queries][FDW]