summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEvan Read <eread@gitlab.com>2018-11-19 06:47:25 +0000
committerEvan Read <eread@gitlab.com>2018-11-19 06:47:25 +0000
commit4693cebbec08d35393784afbb292315fd4d4cbee (patch)
treebc1a672fea5958c443e85f126e7cfb3aa4b53d91
parent98d5a929bf6d4d7bb7d727efe19b547232ddd194 (diff)
parente0f0e8f4348a1fec99cbe4cd6fad7d7ee037e80f (diff)
downloadgitlab-ce-4693cebbec08d35393784afbb292315fd4d4cbee.tar.gz
Merge branch 'fix-requirements' into 'master'
Docs: Fix zero downtime link in requirements See merge request gitlab-org/gitlab-ce!23170
-rw-r--r--doc/install/requirements.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/install/requirements.md b/doc/install/requirements.md
index 97190544c3d..1b7e0d1d0ab 100644
--- a/doc/install/requirements.md
+++ b/doc/install/requirements.md
@@ -104,7 +104,7 @@ features of GitLab work with MySQL/MariaDB:
1. MySQL support for subgroups was [dropped with GitLab 9.3][post].
See [issue #30472][30472] for more information.
1. Geo does [not support MySQL](https://docs.gitlab.com/ee/administration/geo/replication/database.html#mysql-replication). This means no supported Disaster Recovery solution if using MySQL. **[PREMIUM ONLY]**
-1. [Zero downtime migrations][../update/README.md#upgrading-without-downtime] do not work with MySQL.
+1. [Zero downtime migrations](../update/README.md#upgrading-without-downtime) do not work with MySQL.
1. GitLab [optimizes the loading of dashboard events](https://gitlab.com/gitlab-org/gitlab-ce/issues/31806) using [PostgreSQL LATERAL JOINs](https://blog.heapanalytics.com/postgresqls-powerful-new-join-type-lateral/).
1. In general, SQL optimized for PostgreSQL may run much slower in MySQL due to
differences in query planners. For example, subqueries that work well in PostgreSQL