diff --git a/doc/administration/geo/replication/index.md b/doc/administration/geo/replication/index.md index 51c831abaf3552b84a88f3b4cd60c70864b444a4..f1cc9f0df8b183ac8d320839e2b66cdc23f41b37 100644 --- a/doc/administration/geo/replication/index.md +++ b/doc/administration/geo/replication/index.md @@ -117,7 +117,7 @@ The following are required to run Geo: The following operating systems are known to ship with a current version of OpenSSH: - [CentOS](https://www.centos.org) 7.4+ - [Ubuntu](https://ubuntu.com) 16.04+ -- PostgreSQL 11+ with [FDW](https://www.postgresql.org/docs/11/postgres-fdw.html) support and [Streaming Replication](https://wiki.postgresql.org/wiki/Streaming_Replication) +- PostgreSQL 11+ with [Streaming Replication](https://wiki.postgresql.org/wiki/Streaming_Replication) - Git 2.9+ - All nodes must run the same GitLab version. @@ -166,7 +166,6 @@ The tracking database instance is used as metadata to control what needs to be u - Fetch changes from a repository that has recently been updated. Because the replicated database instance is read-only, we need this additional database instance for each **secondary** node. -The tracking database requires the `postgres_fdw` extension. ### Geo Log Cursor diff --git a/doc/install/requirements.md b/doc/install/requirements.md index ac3d37dcc0043841b4a03f25453b87779a8b622f..54fcfeb2ee40380fcd69852762ac856d7365754f 100644 --- a/doc/install/requirements.md +++ b/doc/install/requirements.md @@ -156,10 +156,6 @@ If you're using [GitLab Geo](../administration/geo/replication/index.md): - We strongly recommend running Omnibus-managed instances as they are actively developed and tested. We aim to be compatible with most external (not managed by Omnibus) databases (for example, [AWS Relational Database Service (RDS)](https://aws.amazon.com/rds/)) but we don't guarantee compatibility. -- You must also ensure the `postgres_fdw` extension is loaded into every - GitLab database. This extension - [can be enabled](https://www.postgresql.org/docs/11/sql-createextension.html) - using a PostgreSQL super user. ## Puma settings