Re: Restoring database from backup
От | Adrian Klaver |
---|---|
Тема | Re: Restoring database from backup |
Дата | |
Msg-id | f66398c1-e8b6-49d6-b893-c2c0125b0e2c@aklaver.com обсуждение исходный текст |
Ответ на | Re: Restoring database from backup (Rich Shepard <rshepard@appl-ecosys.com>) |
Ответы |
Re: Restoring database from backup
|
Список | pgsql-general |
On 12/13/24 11:18 AM, Rich Shepard wrote: > On Fri, 13 Dec 2024, Adrian Klaver wrote: > >> This needs more information: >> >> 1) Have you backed up your database at the current state? > > Adrian, > > No, the current state is FUBAR'd. The cron backup script runs each night at > 11:15 p.m. > >> 2) What command did you use to create bustrac-2024-12-12.sql? > > !/usr/bin/bash > # > # This script pg_dump to save the database w/date stamp > > cd /data1/database-backups/ > pg_dump -d bustrac -c -f bustrac-$(date +%Y-%m-%d).sql cd Alright, from here: https://www.postgresql.org/docs/current/app-pgdump.html "-c --clean Output commands to DROP all the dumped database objects prior to outputting the commands for creating them. This option is useful when the restore is to overwrite an existing database. If any of the objects do not exist in the destination database, ignorable error messages will be reported during restore, unless --if-exists is also specified. This option is ignored when emitting an archive (non-text) output file. For the archive formats, you can specify the option when you call pg_restore. " This means when you run the script with: psql -d bustrac -f bustrac-2024-12-12.sql it will clean out the current corrupted objects and replace them with those in the backup file. > > Thanks, > > Rich > > -- Adrian Klaver adrian.klaver@aklaver.com
В списке pgsql-general по дате отправления: