pgsql: HeapTupleHeaderAdjustCmax made the incorrect assumption that the - Mailing list pgsql-committers

From heikki@postgresql.org (Heikki Linnakangas)
Subject pgsql: HeapTupleHeaderAdjustCmax made the incorrect assumption that the
Date
Msg-id 20080901185245.B83C3755325@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
HeapTupleHeaderAdjustCmax made the incorrect assumption that the raw
command id is the cmin, when it can in fact be a combo cid. That made rows
incorrectly invisible to a transaction where a tuple was deleted by multiple
aborted subtransactions.

Report and patch Karl Schnaitter. Back-patch to 8.3, where combo cids was
introduced.

Modified Files:
--------------
    pgsql/src/backend/utils/time:
        combocid.c (r1.4 -> r1.5)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/time/combocid.c?r1=1.4&r2=1.5)

pgsql-committers by date:

Previous
From: petere@postgresql.org (Peter Eisentraut)
Date:
Subject: pgsql: Synchronize the shared object build rules in Makefile.port with
Next
From: heikki@postgresql.org (Heikki Linnakangas)
Date:
Subject: pgsql: HeapTupleHeaderAdjustCmax made the incorrect assumption that the