Re: Base Backups from PITR Standby
От | Tom Lane |
---|---|
Тема | Re: Base Backups from PITR Standby |
Дата | |
Msg-id | 16140.1193720810@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Base Backups from PITR Standby (Brian Wipf <brian@clickspace.com>) |
Ответы |
Re: Base Backups from PITR Standby
|
Список | pgsql-general |
Brian Wipf <brian@clickspace.com> writes: > The process I use that leads to the warnings is simple: > I use pg_controldata to determine the current checkpoint WAL location > of the standby server. I ensure I have this WAL file and all newer > WALs. I backup all files under the standby's database cluster > directory, including all tablespaces, which are soft linked. I restore > the database cluster directory to its new location and create soft > links in pg_tblspc to point to the proper tablespace directories just > backed up. I create the pg_xlog directory containing an archive_status > directory. This seems not exactly per spec. Why are you not using pg_start_backup and pg_stop_backup around the copying of the database files? regards, tom lane
В списке pgsql-general по дате отправления: