From: | Mark Kirkwood <markir(at)coretech(dot)co(dot)nz> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Proposal for Recover mode in pg_ctl (in 8.0) |
Date: | 2004-11-07 00:54:06 |
Message-ID: | 418D722E.1080902@coretech.co.nz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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'
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Kirkwood | 2004-11-07 01:03:14 | Re: Proposal for Recover mode in pg_ctl (in 8.0) |
Previous Message | Greg Stark | 2004-11-07 00:28:16 | Re: Increasing the length of pg_stat_activity.current_query... |