On 01.11.2013 11:42, Mika Eloranta wrote:
pg_receivexlog calculated the xlog segment number incorrectly
when started after the previous instance was interrupted.
Resuming streaming only worked when the physical wal segment
counter was zero, i.e. for the first 256 segments or so.
Oops. Fixed, thanks for the report!
It's a bit scary that this bug went unnoticed for this long; it was
introduced quite early in the 9.3 development cycle. Seems that I did
all the testing of streaming timeline changes with pg_receivexlog later
in 9.3 cycle with segment numbers < 256, and no-one else have done
long-running tests with pg_receivexlog either.
- Heikki
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
