@@ -97,7 +97,7 @@ Follow the below instructions to ensure you use the most up to date requirements
...
@@ -97,7 +97,7 @@ Follow the below instructions to ensure you use the most up to date requirements
#### Check for InnoDB File-Per-Table Tablespaces
#### Check for InnoDB File-Per-Table Tablespaces
We need to check, enable and maybe convert your existing GitLab DB tables to the [InnoDB File-Per-Table Tablespaces](http://dev.mysql.com/doc/refman/5.7/en/innodb-multiple-tablespaces.html) as a prerequisite for supporting **utfb8mb4 with long indexes** required by recent GitLab databases.
We need to check, enable and maybe convert your existing GitLab DB tables to the [InnoDB File-Per-Table Tablespaces](https://dev.mysql.com/doc/refman/5.7/en/innodb-multiple-tablespaces.html) as a prerequisite for supporting **utfb8mb4 with long indexes** required by recent GitLab databases.
# Login to MySQL
# Login to MySQL
mysql -u root -p
mysql -u root -p
...
@@ -134,7 +134,7 @@ We need to check, enable and maybe convert your existing GitLab DB tables to the
...
@@ -134,7 +134,7 @@ We need to check, enable and maybe convert your existing GitLab DB tables to the
> You need **MySQL 5.5.3 or later** to perform this update.
> You need **MySQL 5.5.3 or later** to perform this update.
Whatever the results of your checks above, we now need to check if your GitLab database has been created using [InnoDB File-Per-Table Tablespaces](http://dev.mysql.com/doc/refman/5.7/en/innodb-multiple-tablespaces.html)(i.e.`innodb_file_per_table` was set to **1** at initial setup time).
Whatever the results of your checks above, we now need to check if your GitLab database has been created using [InnoDB File-Per-Table Tablespaces](https://dev.mysql.com/doc/refman/5.7/en/innodb-multiple-tablespaces.html)(i.e.`innodb_file_per_table` was set to **1** at initial setup time).
NOTE: **Note:**
NOTE: **Note:**
This setting is [enabled by default](http://dev.mysql.com/doc/refman/5.7/en/innodb-parameters.html#sysvar_innodb_file_per_table) since MySQL 5.6.6.
This setting is [enabled by default](http://dev.mysql.com/doc/refman/5.7/en/innodb-parameters.html#sysvar_innodb_file_per_table) since MySQL 5.6.6.
...
@@ -163,7 +163,7 @@ Now, if you have a **different result** returned by the 2 commands above, it mea
...
@@ -163,7 +163,7 @@ Now, if you have a **different result** returned by the 2 commands above, it mea
-**Case 2: a result equals to "0" OR not the same result for both commands**
-**Case 2: a result equals to "0" OR not the same result for both commands**
Unfortunately, none or only some of your GitLab database tables use the GitLab requirement of [InnoDB File-Per-Table Tablespaces](http://dev.mysql.com/doc/refman/5.7/en/innodb-multiple-tablespaces.html).
Unfortunately, none or only some of your GitLab database tables use the GitLab requirement of [InnoDB File-Per-Table Tablespaces](https://dev.mysql.com/doc/refman/5.7/en/innodb-multiple-tablespaces.html).
Let's enable what we need on the running server:
Let's enable what we need on the running server:
...
@@ -297,8 +297,7 @@ GitLab database to `longtext` columns, which can persist values of up to 4GB
...
@@ -297,8 +297,7 @@ GitLab database to `longtext` columns, which can persist values of up to 4GB
(sometimes less if the value contains multibyte characters).
(sometimes less if the value contains multibyte characters).
Details can be found in the [PostgreSQL][postgres-text-type] and
Details can be found in the [PostgreSQL][postgres-text-type] and
-`unknown_git` user will be used as the commit author if the GitLab user does not exist in
-`unknown_git` user will be used as the commit author if the GitLab user does not exist in
Perforce Helix.
Perforce Helix.
Read about [Git Fusion settings on Perforce.com](https://www.perforce.com/perforce/doc.current/manuals/git-fusion/Content/Git-Fusion/section_zdp_zz1_3l.html).
Read about [Git Fusion settings on Perforce.com](https://www.perforce.com/perforce/doc.current/manuals/git-fusion/Content/Git-Fusion/section_vss_bdw_w3.html#section_zdp_zz1_3l).