summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorStan Hu <stanhu@gmail.com>2017-06-08 20:01:38 +0000
committerStan Hu <stanhu@gmail.com>2017-06-08 20:01:38 +0000
commitaf16177707418ff9a4f96c0fee95b3788d153474 (patch)
tree215c9687c43b890fe141a3dae4d465aeef2fc864
parent4b1c49171dcdac5ba78a81bad94776644d9dbed5 (diff)
parent09f1530f84e2c738199967c5553cf581d8203dfc (diff)
downloadgitlab-ce-af16177707418ff9a4f96c0fee95b3788d153474.tar.gz
Merge branch 'evn-no-geo-either' into 'master'
GitLab GEO also does not support mysql replication See merge request !11914
-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..197a92905c8 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. GitLab Geo also does [not support MySQL](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