On 2013-11-29 16:30:08 -0300, Alvaro Herrera wrote: > New versions of all these patches, plus one more patch which removes the > behavior that HeapTupleGetUpdateXid checks for aborted updates.
> From 0dce0b75da2732ca93f4c451b9bae6d4416794c3 Mon Sep 17 00:00:00 2001 > From: Alvaro Herrera <alvhe...@alvh.no-ip.org> > Date: Fri, 29 Nov 2013 16:08:06 -0300 > Subject: [PATCH 4/5] Don't TransactionIdDidAbort in HeapTupleGetUpdateXid > > It is dangerous to do so, because some code expects to be able to see what's > the true Xmax even if it is aborted (particularly while traversing HOT > chains). So don't do it, and instead rely on the callers to verify for > abortedness, if necessary. > > Several race conditions and bugs fixed in the process. The current version of that additional patch causes two failures in isolationtester's delete-abort-savept.spec/out. But afaics the old behaviour was a bug: An updater seems to have waited for an aborted subtransaction. Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, 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
