Re: Pgbasebackup help
От | Jim Nasby |
---|---|
Тема | Re: Pgbasebackup help |
Дата | |
Msg-id | 565F7DF1.7070007@BlueTreble.com обсуждение исходный текст |
Ответ на | Re: Pgbasebackup help (David Steele <david@pgmasters.net>) |
Ответы |
Re: Pgbasebackup help
|
Список | pgsql-general |
On 12/2/15 1:56 PM, David Steele wrote: >> >Also, I don’t want enable archive_mode = on as it needs to maintain >> >archives files. > As it turns out, archiving would be the solution to your problem. If > you were archiving you could restore a*previous* backup and then replay > WAL to exactly T3. There might be some jitter from clock differences > but it should have the desired effect. And in this case previous could be a PG backup taken immediately before the backup of the private DBMS. I don't remember off-hand if pg_basebackup has an option for delaying the pg_stop_backup() call, but if it does then I think the simplest thing is to just delay that until after your private DBMS backup is complete. -- Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX Experts in Analytics, Data Architecture and PostgreSQL Data in Trouble? Get it in Treble! http://BlueTreble.com
В списке pgsql-general по дате отправления: