2014-05-08 11:18:12 +00:00
# Migrating GitLab from MySQL to Postgres
2014-04-24 22:48:22 +00:00
If you are replacing MySQL with Postgres while keeping GitLab on the same server all you need to do is to export from MySQL, import into Postgres and rebuild the indexes as described below. If you are also moving GitLab to another server, or if you are switching to omnibus-gitlab, you may want to use a GitLab backup file. The second part of this documents explains the procedure to do this.
2014-03-17 13:55:56 +00:00
2014-05-08 10:10:04 +00:00
## Export from MySQL and import into Postgres
Use this if you are keeping GitLab on the same server.
2014-03-17 13:55:56 +00:00
```
2014-05-08 11:18:22 +00:00
sudo service gitlab stop
# Update /home/git/gitlab/config/database.yml
2014-05-19 15:49:29 +00:00
git clone https://github.com/gitlabhq/mysql-postgresql-converter.git
2014-03-17 13:55:56 +00:00
cd mysql-postgresql-converter
mysqldump --compatible=postgresql --default-character-set=utf8 -r databasename.mysql -u root gitlabhq_production
python db_converter.py databasename.mysql databasename.psql
psql -f databasename.psql -d gitlabhq_production
2014-05-08 11:18:22 +00:00
2014-05-19 15:51:58 +00:00
# Rebuild indexes (see below)
2014-05-08 11:18:22 +00:00
sudo service gitlab start
2014-03-17 13:55:56 +00:00
```
2014-05-08 10:10:04 +00:00
2014-05-19 15:51:58 +00:00
## Rebuild indexes
2014-04-24 22:48:22 +00:00
The lanyrd database converter script does not preserve all indexes, so we have to recreate them ourselves after migrating from MySQL. It is not necessary to shut down GitLab for this process.
2014-05-28 15:09:20 +00:00
2014-05-29 13:42:20 +00:00
### For non-omnibus installations
2014-05-28 15:09:20 +00:00
2014-04-24 22:48:22 +00:00
On non-omnibus installations (distributed using Git) we retrieve the index declarations from version control using `git stash` .
2014-05-28 15:09:20 +00:00
2014-05-19 15:51:58 +00:00
```
# Clone the database converter on your Postgres-backed GitLab server
cd /tmp
git clone https://github.com/gitlabhq/mysql-postgresql-converter.git
cd /home/git/gitlab
2014-05-28 15:09:20 +00:00
# Stash changes to db/schema.rb to make sure we can find the right index statements
2014-05-19 15:51:58 +00:00
sudo -u git -H git stash
2014-05-28 15:09:20 +00:00
# Generate add_index.rb
ruby /tmp/mysql-postgresql-converter/add_index_statements.rb db/schema.rb > /tmp/mysql-postgresql-converter/add_index.rb
# Create the indexes
sudo -u git -H bundle exec rails runner -e production 'eval $stdin.read' < /tmp/mysql-postgresql-converter/add_index.rb
```
### For omnibus-gitlab installations
2014-04-24 22:48:22 +00:00
On omnibus-gitlab we need to get the index declarations from a file called `schema.rb.bundled` . For versions older than 6.9, we need to download the file.
2014-05-28 15:09:20 +00:00
```
# Clone the database converter on your Postgres-backed GitLab server
cd /tmp
/opt/gitlab/embedded/bin/git clone https://github.com/gitlabhq/mysql-postgresql-converter.git
cd /tmp/mysql-postgresql-converter
2014-05-29 13:42:20 +00:00
# Download schema.rb.bundled if necessary
test -e /opt/gitlab/embedded/service/gitlab-rails/db/schema.rb.bundled || sudo /opt/gitlab/embedded/bin/curl -o /opt/gitlab/embedded/service/gitlab-rails/db/schema.rb.bundled https://gitlab.com/gitlab-org/gitlab-ce/raw/v6.9.1/db/schema.rb
2014-05-28 15:09:20 +00:00
# Generate add_index.rb
/opt/gitlab/embedded/bin/ruby add_index_statements.rb /opt/gitlab/embedded/service/gitlab-rails/db/schema.rb.bundled > add_index.rb
2014-05-29 13:42:20 +00:00
# Create the indexes
2014-05-28 15:09:20 +00:00
/opt/gitlab/bin/gitlab-rails runner 'eval $stdin.read' < add_index.rb
2014-05-19 15:51:58 +00:00
```
2014-05-08 10:10:04 +00:00
## Converting a GitLab backup file from MySQL to Postgres
2014-04-24 22:48:22 +00:00
GitLab backup files (< timestamp > _gitlab_backup.tar) contain a SQL dump. Using the lanyrd database converter we can replace a MySQL database dump inside the tar file with a Postgres database dump. This can be useful if you are moving to another server.
2014-05-08 10:10:04 +00:00
```
# Stop GitLab
sudo service gitlab stop
# Create the backup
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
# Note the filename of the backup that was created. We will call it
# TIMESTAMP_gitlab_backup.tar below.
# Move the backup file we will convert to its own directory
sudo -u git -H mkdir -p tmp/backups/postgresql
sudo -u git -H mv tmp/backups/TIMESTAMP_gitlab_backup.tar tmp/backups/postgresql/
# Create a separate database dump with PostgreSQL compatibility
cd tmp/backups/postgresql
sudo -u git -H mysqldump --compatible=postgresql --default-character-set=utf8 -r gitlabhq_production.mysql -u root gitlabhq_production
# Clone the database converter
2014-07-03 10:17:46 +00:00
sudo -u git -H git clone https://github.com/gitlabhq/mysql-postgresql-converter.git
2014-05-08 10:10:04 +00:00
# Convert gitlabhq_production.mysql
sudo -u git -H mkdir db
sudo -u git -H python mysql-postgresql-converter/db_converter.py gitlabhq_production.mysql db/database.sql
# Replace the MySQL dump in TIMESTAMP_gitlab_backup.tar.
# Warning: if you forget to replace TIMESTAMP below, tar will create a new file
# 'TIMESTAMP_gitlab_backup.tar' without giving an error.
sudo -u git -H tar rf TIMESTAMP_gitlab_backup.tar db/database.sql
2014-05-19 15:51:58 +00:00
# Done! TIMESTAMP_gitlab_backup.tar can now be restored into a Postgres GitLab
# installation. Remember to recreate the indexes after the import.
2014-05-08 10:10:04 +00:00
```