Re: Proposal for Recover mode in pg_ctl (in 8.0)
От | Mark Kirkwood |
---|---|
Тема | Re: Proposal for Recover mode in pg_ctl (in 8.0) |
Дата | |
Msg-id | 418D722E.1080902@coretech.co.nz обсуждение исходный текст |
Ответ на | Re: Proposal for Recover mode in pg_ctl (in 8.0) (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Proposal for Recover mode in pg_ctl (in 8.0)
|
Список | pgsql-hackers |
While this is nice, it will not help you if the restoration directory is different from your archive directory. That is : restore_command in recovery.conf fetches from somewhere other than where archive_command in postgresql.conf copied. I am not sure how likely this situation is, but setting up log shipping, or maybe recovering from disk failure *might* mean you need to bring the saved archive files "back from somewhere else". regards Mark Tom Lane wrote: > >Another and simpler way is to recommend that people use archive_command >strings that won't overwrite an existing archive file. > >For instance instead of showing the example >archive_command = 'cp %p /mnt/server/archivedir/%f' >we could show >archive_command = 'test ! -f /mnt/server/archivedir/%f && cp %p /mnt/server/archivedir/%f' > > >
В списке pgsql-hackers по дате отправления: