delta/gitlab/gitlab-ce.git/lib/backup/database.rb, branch api-groups

Add CRON=1 backup setting for quiet backups

2014-11-20T14:46:04+00:00

Drop all Postgres sequences during backup restore

2014-10-28T17:52:21+00:00

Fail harder in the backup script

2014-10-01T13:43:27+00:00

This change also shows the output of failed Git commands during the
backup.

Drop all tables before restoring a PostgreSQL DB

2014-03-28T12:44:46+00:00

Invoking 'db:schema:load' turned out to be a bad idea: when downgrading
an existing GitLab installation, the schema of the newer version would
be preserved when trying to import the old version.

Empty the database during Postgres backup restore

2014-02-26T17:26:31+00:00

The expected behavior during a GitLab backup restore is to overwrite
existing database data. This works for MySQL because the output of
mysqldump contains 'DROP TABLE IF EXISTS' statements. pg_dump on the
other hand assumes that one will restore into an empty database. When
this is not the case, during the restore with psql some of the data will
be skipped if existing data is 'in the way'. By first invoking `rake
db:schema:load` during a Postgres GitLab backup restore, we make sure
that all important data is correctly restored.

Report failure of DB backup commands

2014-01-23T10:19:43+00:00

Remove Bourne shell from backup code

2013-11-06T13:02:28+00:00

Revert "More escaping"

2013-11-05T13:35:49+00:00

This reverts commit c46eaca91247ccf8e6fb3b691dad028e1b084ae3.

More escaping

2013-11-04T22:09:03+00:00

- Database name may contain characters which are not shell friendly
- Database password could contain the same
- While we at it there is no harm in escaping generated paths too
- Refactored 2-line system(command)

Signed-off-by: Nigel Kukard

Fix PostgreSQL database restoration problem (#4217)

2013-06-10T11:06:12+00:00

Use psql instead of pg_restore to restore SQL dump file.