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'
>
>
>
