On Thu, Feb 12, 2015 at 4:18 PM, Andres Freund <and...@2ndquadrant.com> wrote: > No need for debugging. It's plain and simply a (cherry-pick) conflict I > resolved wrongly during backpatching. 9.3, 9.4 and master do not have > that problem. That whole fix was quite painful because every single > release had significantly different code :(. pg_basebackup/ is pretty > messy. > I'm not sure why my testsuite didn't trigger that problem. Possibly > because a retry makes things work :( > > Somewhat uckily it's 9.2 only (9.3, 9.4 and master look correct, earlier > releases don't have pg_receivexlog) and can quite easily be worked > around by creating the archive_status directory.
The workaround works perfectly for me in this case, I'm going to updrade it up to 9.4 anyway soon. Thank you, Andres. -- Kind regards, Sergey Konoplev PostgreSQL Consultant and DBA http://www.linkedin.com/in/grayhemp +1 (415) 867-9984, +7 (499) 346-7196, +7 (988) 888-1979 gray...@gmail.com -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers