On Thu, Apr 9, 2015 at 11:02 PM, <eshkinkot@gmail.com> wrote:
> I do not use streaming, only WAL archive and after promote standby
> it try to archive WALs with old timeline, but I already have it in
> archive (from old master) and at new master WAL archiving stopped.
>
> [...]
> now WAL archiving stopped with messages:
>
> 2015-04-08 20:49:31 MSK LOG: archive command failed with exit code 1
> 2015-04-08 20:49:31 MSK DETAIL: The failed archive command was: test ! -f
> ~/tmp/pg-slave-switch/w/000000010000000000000025 && cp
> pg_xlog/000000010000000000000025
> ~/tmp/pg-slave-switch/w/000000010000000000000025
> 2015-04-08 20:49:32 MSK LOG: archive command failed with exit code 1
The standby has recycled some WAL segments ahead thinking to reuse
them and at promotion they became actually bogus. It is an expected
behavior for a standby to archive the files that it thinks are not
archived yet after promotion even if they are not of its own timeline,
but those bogus segments should never be archived. See this thread for
example that has a patch:
http://www.postgresql.org/message-id/54942034.7080303@vmware.com
Note that I got this patch on my list-of-things-to-look-at for some
time, perhaps it is time to accelerate the move.
Regards,
--
Michael