delta/gitlab/gitlab-ce.git/lib/backup/database.rb, branch parallel-tests

Remove superfluous mkdir -p

2015-10-06T13:38:21+00:00

Keep old path: db/database.sql.gz

2015-10-06T13:21:15+00:00

Documentation elsewhere refers to this internal path, let's keep
it.

Reduce disk IO during SQL backup

2015-10-06T13:06:15+00:00

By using light gzip compression we can save a lot of disk IO during
the backup.

add pg_schema to backup config

2015-09-18T13:29:13+00:00

Do not delete the SQL dump too early

2015-08-21T14:12:46+00:00

The change in baa157926d432f404a41c31ad6514ff8d5366269 broke backup
restore fucnctionality. This would not lead to data loss, but it
prevented the restore script from working. This bug exists only in
7.14.0 release candidate versions, not in 7.13.

Reported in https://github.com/gitlabhq/gitlabhq/issues/9571 .

Workaround the warnings emitted by MySQL 5.6 regarding password on the

2015-08-12T14:51:24+00:00

command line.

Stricter mkdir's in 'rake gitlab:backup:create'

2015-07-30T08:17:34+00:00

Set internal backup directory modes on create

2015-07-29T09:18:55+00:00

This sidesteps problems with running 'chmod' on some CIFS mounts.

Don't stop if database.sql.gz already exists

2015-07-21T08:37:27+00:00

The existing behavior of the backups is to overwrite whatever data
was still there in the scratch directories. This broke when we added
a 'gzip' step because 'gzip database.sql' will fail if 'database.sql.gz'
already exists. Doing 'rm -f database.sql.gz' before the 'gzip'
avoids this failure.

Merge branch 'improve-postgres-restore-cleaning' into 'master'

2015-07-07T23:02:48+00:00


Use native Postgres database cleaning during backup restore

We were using hacks to drop tables etc during a Postgres backup
restore. With this change, we let pg_dump insert the DROP TABLE
statements it needs at the start of the SQL dump.

See merge request !1891