On Fri, Jun 23, 2017 at 3:17 PM, Amit Langote <langote_amit...@lab.ntt.co.jp> wrote: > Initially, I had naively set wal_consistency_check = all before running > make installcheck and then had to wait for a long time to confirm that WAL > generated by the gin test indeed caused consistency check failure on the > standby with the v1 patch.
wal_consistency_check = gin would have saved you a lot of I/O. > But I can see Sawada-san's point that there should be some way for > developers writing code that better had gone through WAL consistency > checking facility to do it without much hassle. But then again, it may > not be that frequent to need that. Yeah, I have my own set of generic scripts for that. There could be a set of modules out of the main check-world, the risk that those finish rotting is high though... -- Michael -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers