On Wed, Jun 15, 2016 at 10:03 AM, Masahiko Sawada <sawada.m...@gmail.com> wrote: >> I'm not sure what to do about this: this part of the heap_update() >> logic has been like this forever, and I assume that if it were easy to >> refactor this away, somebody would have done it by now. > > How about changing collect_corrupt_items to acquire > AccessExclusiveLock for safely checking?
Well, that would make it a lot less likely for pg_check_{visible,frozen} to detect the bug in heap_update(), but it wouldn't fix the bug in heap_update(). -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers