On Thu, Nov 9, 2017 at 8:25 AM, Asim Praveen <aprav...@pivotal.io> wrote: > Indeed, the assertion tripped during WAL replay on the standby. This was > caught by TAP tests under src/test/recovery. The assertion is now fixed so > that WAL replay is exempt from the check. Please find the new patch > attached. The tests now pass with the fix. I also manually verified that > recovery works with "wal_consistency_checking=all".
I still have a bad feeling about that bit... Still, it does not change the fact that patch 0001 in https://www.postgresql.org/message-id/CANXE4TccH_VjdKaHc9=KyH0Y7WORqZN+=mH5f=mp0bw3gzx...@mail.gmail.com needs a committer per the fact that it visibly fixes incorrect backend code and API contract. So I am switching the CF entry to ready for committer, but only for 0001. The other things could always be taken care of later. -- Michael -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
