summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorYorick Peterse <yorickpeterse@gmail.com>2017-05-12 15:48:06 +0200
committerYorick Peterse <yorickpeterse@gmail.com>2017-05-12 15:48:06 +0200
commitcab734a80f32321cd4775bd73adcae9fddceb56b (patch)
tree889aa5dccab8f98c29a54a79737551730817eebb
parent99f36c2ca69de17235eeab53f510753b6c1ae7c4 (diff)
downloadgitlab-ce-add-problematic-mysql-examples.tar.gz
Link to a case where we can't support MySQLadd-problematic-mysql-examples
This updates the requirements guide to include a link to an issue where we discuss dropping MySQL support for nested groups. This should give users a better understanding of why we highly recommend them to use PostgreSQL instead. [ci skip]
-rw-r--r--doc/install/requirements.md7
1 files changed, 5 insertions, 2 deletions
diff --git a/doc/install/requirements.md b/doc/install/requirements.md
index 148796b73d4..2e456557d77 100644
--- a/doc/install/requirements.md
+++ b/doc/install/requirements.md
@@ -126,8 +126,11 @@ We currently support the following databases:
- MySQL/MariaDB
We _highly_ recommend the use of PostgreSQL instead of MySQL/MariaDB as not all
-features of GitLab may work with MySQL/MariaDB. Existing users using GitLab with
-MySQL/MariaDB are advised to migrate to PostgreSQL instead.
+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
+migrate to PostgreSQL instead.
The server running the database should have _at least_ 5-10 GB of storage
available, though the exact requirements depend on the size of the GitLab