On Thu, Feb 7, 2013 at 8:38 PM, Alvaro Herrera <alvhe...@2ndquadrant.com> wrote: > Alvaro Herrera escribió: >> Alvaro Herrera escribió: >> >> > Hm, if the foreign key patch is to blame, this sounds like these tuples >> > had a different set of XMAX hint bits and a different Xmax, and they >> > were clobbered by something like vacuum or page pruning. >> >> Hm, I think heap_freeze_tuple is busted, yes. > > This patch seems to fix the problem for me. Please confirm.
Applied to 0ac5ad5134f276, it has survived 4 wrap-arounds so far without problem. I will let it go for a while longer, but I think we can assume it is fixed. Cheers, Jeff -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
