summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKai Schröer <kai.schroeer@gmx.net>2018-11-18 12:44:48 +0000
committerKai Schröer <kai.schroeer@gmx.net>2018-11-18 12:44:48 +0000
commite0f0e8f4348a1fec99cbe4cd6fad7d7ee037e80f (patch)
tree7008209464636c9a96278c4606523c17cc94c256
parent29d8179ba07be3ed111f939285eb4064d84cb7df (diff)
downloadgitlab-ce-e0f0e8f4348a1fec99cbe4cd6fad7d7ee037e80f.tar.gz
Fix zero downtime link in requirements
-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