summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorStan Hu <stanhu@gmail.com>2017-08-11 15:34:15 -0700
committerStan Hu <stanhu@gmail.com>2017-08-11 15:37:19 -0700
commit057052142099cb24f103317010ca17ea64f9f2ce (patch)
tree000041301486078274183328e8bf3ff0cfaf2864
parent3254ad4d5a4c8114d0580b64aafeb24bd8abf926 (diff)
downloadgitlab-ce-057052142099cb24f103317010ca17ea64f9f2ce.tar.gz
Add notes about database performance for MySQL
[ci skip]
-rw-r--r--doc/install/requirements.md4
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/install/requirements.md b/doc/install/requirements.md
index 141df55f6bc..175dfc62096 100644
--- a/doc/install/requirements.md
+++ b/doc/install/requirements.md
@@ -104,6 +104,10 @@ features of GitLab work with MySQL/MariaDB:
See [issue #30472][30472] for more information.
1. GitLab Geo does [not support MySQL](https://docs.gitlab.com/ee/gitlab-geo/database.html#mysql-replication).
1. [Zero downtime migrations][zero] 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
+ may not be [performant in MySQL](https://dev.mysql.com/doc/refman/5.7/en/optimizing-subqueries.html)
1. We expect this list to grow over time.
Existing users using GitLab with MySQL/MariaDB are advised to