Sorry, in the second paragraph I meant to say "it always archives the last replayed one, although that file was already archived and has not changed because another timeline is started."
Daniel
On 18 July 2013 09:58, Daniel Gomez Blanco <nanodgb@gmail.com> wrote:
Hi Amul,
No, I didn't copy my postgres.conf from master to standby. This is always working on a single instance, archiving WAL files to be able to achieve backup and recovery.
The problem arises after recovery. We go back to a certain snapshot (created between pg_start_backup and pg_stop_backup as advised) and then start replaying logs. It reaches a consistent state after the pg_stop_backup point and all the rest of the logs are replayed, and recovery is successful. But after that, when the database starts up and starts recycling WAL files, it always archives the last replayed one, although that file was already archived and has changed because another timeline is started.
For the moment, I solved the problem modifying the archive_command to 'test -f /.../archive/%f || cp %p /.../archive/%f' so if the file exists it doesn't archive it. But that is not the recommended procedure in the documentation, where it says that a the archive command should fail if a fail is tried to be archived twice.
