summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorernstvn <ernst@gitlab.com>2017-06-05 14:20:33 -0700
committerernstvn <ernst@gitlab.com>2017-06-05 14:20:33 -0700
commitee828f2947e69d37a4c239f83bf49b96df59ecf1 (patch)
treeee0fc29cc4eb70e62029daa588822bf416a1f122
parent5578506eb1e7e911fa7b283e81b3751be370977b (diff)
downloadgitlab-ce-ee828f2947e69d37a4c239f83bf49b96df59ecf1.tar.gz
GitLab GEO also does not support mysql replication
-rw-r--r--doc/install/requirements.md3
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/install/requirements.md b/doc/install/requirements.md
index 5338ccb9d3a..c25776c0adb 100644
--- a/doc/install/requirements.md
+++ b/doc/install/requirements.md
@@ -129,7 +129,8 @@ We _highly_ recommend the use of PostgreSQL instead of MySQL/MariaDB as not all
features of GitLab may work with MySQL/MariaDB. For example, MySQL does not have
the right features to support nested groups in an efficient manner; see
<https://gitlab.com/gitlab-org/gitlab-ce/issues/30472> for more information
-about this. Existing users using GitLab with MySQL/MariaDB are advised to
+about this. In GitLab Geo, MySQL replication is also [not supported](https://docs.gitlab.com/ee/gitlab-geo/database.html#mysql-replication).
+Existing users using GitLab with MySQL/MariaDB are advised to
migrate to PostgreSQL instead.
The server running the database should have _at least_ 5-10 GB of storage