Gitlab will start from the 12.1 version is no longer supported MySQL!
Gitlab official announcement, version 12.1 will begin no longer supports MySQL database.
HTTP: // news.51cto.com/art/201907/598982.htm Each database has his shortcomings.
Gitlab official announcement, version 12.1 will begin no longer supports MySQL database. As early as July 2017, Gitlab plans to abandon support for MySQL. At present, this decision will begin in version 12.1.
Official lists several MySQL can not meet the requirements of local Gitlab:
- Can not support nested group query ( details )
- We must use technology to enhance the limit MySQL black columns, which will result in denial MySQL to store data
- MySQL can not add
TEXTtype field length limit - MySQL does not support partitioned indexes
- There are similar Geo
To solve these problems above, Gitlab created a number of specialized codes for MySQL. In some cases, this led to the merger of the complexity of the request to be twice as high, because they have to support a second database back end. Creating and maintaining these codes consume our cycle time and speed, and will reduce our iteration.
It also allows us to slow down, because our CI system will run our test suite twice, once each backend. Delete support for MySQL can shorten the time CI operations and reduce costs. These costs will eventually become considerable.
All in all, Gitlab that supports both MySQL and PostgreSQL two databases, the development team feel bored.
In addition, it Gitlab survey found that use MySQL multi-user version of the previous 11.
So, if you want to upgrade to version Gitlab 12.1, then you are old MySQL database may make you more painful. You can refer to the official Migration Guidelines.