From 3376af6bd9b25b6bba9669a0c3edc878a954a54d Mon Sep 17 00:00:00 2001 From: Marcel Amirault Date: Thu, 6 Jun 2019 02:26:50 +0000 Subject: Docs: Update anchor to more recent section in geo db doc --- doc/administration/geo/replication/database.md | 3 +-- 1 file changed, 1 insertion(+), 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] -- cgit v1.2.1