pgsql: Reduce spurious Hot Standby conflicts from never-visible records - Mailing list pgsql-committers

From Simon Riggs
Subject pgsql: Reduce spurious Hot Standby conflicts from never-visible records
Date
Msg-id E1PQwyA-0006L7-EO@gemulon.postgresql.org
Whole thread Raw
Responses Re: pgsql: Reduce spurious Hot Standby conflicts from never-visible records  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
Reduce spurious Hot Standby conflicts from never-visible records.
Hot Standby conflicts only with tuples that were visible at
some point. So ignore tuples from aborted transactions or for
tuples updated/deleted during the inserting transaction when
generating the conflict transaction ids.

Following detailed analysis and test case by Noah Misch.
Original report covered btree delete records, correctly observed
by Heikki Linnakangas that this applies to other cases also.
Fix covers all sources of cleanup records via common code.
Includes additional fix compared to commit on HEAD

Branch
------
REL9_0_STABLE

Details
-------
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=a804a23e7af0e075b88e7b03bfd9b0f22d2657b2

Modified Files
--------------
src/backend/access/heap/heapam.c    |   31 +++++++++++++++++++++++--------
src/backend/access/heap/pruneheap.c |    1 -
src/backend/access/nbtree/nbtxlog.c |   19 +++++--------------
3 files changed, 28 insertions(+), 23 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Eliminate O(N^2) behavior in parallel restore with many blobs.
Next
From: Tom Lane
Date:
Subject: pgsql: Fix efficiency problems in tuplestore_trim().