Re: BUG #8450: pg_basebackup blocks until WAL archiving successful
От | Heikki Linnakangas |
---|---|
Тема | Re: BUG #8450: pg_basebackup blocks until WAL archiving successful |
Дата | |
Msg-id | 523FFCEF.4040302@vmware.com обсуждение исходный текст |
Ответ на | BUG #8450: pg_basebackup blocks until WAL archiving successful (stuart@stuartbishop.net) |
Ответы |
Re: BUG #8450: pg_basebackup blocks until WAL archiving successful
|
Список | pgsql-bugs |
On 13.09.2013 15:13, stuart@stuartbishop.net wrote: > pg_basebackup blocks until all necessary WAL files have been archived by > archive_command. This can take a few minutes under normal circumstances, and > indefinitely if archive_command is failing. > > I would like to be able to disable this check, as I am streaming backups to > a system that can time out my connection if it does not receive new data for > a short while. This makes unattended backups problematic. I can see why you'd want that, but it seems equally problematic to let pg_basebackup return, when the WAL files haven't been archived yet and you therefore don't in fact have valid, restorable backup yet. Have you considered using the --xlog-method=stream option, to include the WAL files in the backup? That will make your backups somewhat larger, as the WAL files are included, but in that mode pg_basebackup won't wait for the archival and the backup will be restorable even if archive_command is failing. - Heikki
В списке pgsql-bugs по дате отправления: