pgsql: Cope with heap_fetch failure while locking an update chain - Mailing list pgsql-committers

From Alvaro Herrera
Subject pgsql: Cope with heap_fetch failure while locking an update chain
Date
Msg-id E1Vm36s-00022b-GZ@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Cope with heap_fetch failure while locking an update chain

The reason for the fetch failure is that the tuple was removed because
it was dead; so the failure is innocuous and can be ignored.  Moreover,
there's no need for further work and we can return success to the caller
immediately.  EvalPlanQualFetch is doing something very similar to this
already.

Report and test case from Andres Freund in
20131124000203.GA4403@alap2.anarazel.de

Branch
------
REL9_3_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/fbface6f946242571f4acbfa9a74727c073748ba

Modified Files
--------------
src/backend/access/heap/heapam.c |   11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)


pgsql-committers by date:

Previous
From: Alvaro Herrera
Date:
Subject: pgsql: Cope with heap_fetch failure while locking an update chain
Next
From: Alvaro Herrera
Date:
Subject: pgsql: Compare Xmin to previous Xmax when locking an update chain