Peter Geoghegan wrote: > On Thu, Sep 28, 2017 at 7:47 AM, Alvaro Herrera <alvhe...@alvh.no-ip.org> > wrote: > > Fix freezing of a dead HOT-updated tuple > > If I run Dan Wood's test case again, the obvious symptom (spurious > duplicates) goes away. However, the enhanced amcheck, and thus CREATE > INDEX/REINDEX, still isn't happy about this: > > postgres=# select bt_index_check('t_pkey', true); > DEBUG: 00000: verifying presence of required tuples in index "t_pkey" > LOCATION: bt_check_every_level, verify_nbtree.c:424 > ERROR: XX000: failed to find parent tuple for heap-only tuple at > (0,6) in table "t" > LOCATION: IndexBuildHeapRangeScan, index.c:2597 > Time: 3.699 ms
... Rats, I obviously missed the message where you said that amcheck detected this problem. Odd that it's not fixed. I guess there's still some more work to do here ... -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers