Skip site navigation (1) Skip section navigation (2)

pgsql: Correctly detect SSI conflicts of prepared transactions aftercr

From: Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Correctly detect SSI conflicts of prepared transactions aftercr
Date: 2012-02-29 13:55:17
Message-ID: E1S2jzx-0007oY-7t@gemulon.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Correctly detect SSI conflicts of prepared transactions after crash.

A prepared transaction can get new conflicts in and out after preparing, so
we cannot rely on the in- and out-flags stored in the statefile at prepare-
time. As a quick fix, make the conservative assumption that after a restart,
all prepared transactions are considered to have both in- and out-conflicts.
That can lead to unnecessary rollbacks after a crash, but that shouldn't be
a big problem in practice; you don't want prepared transactions to hang
around for a long time anyway.

Dan Ports

Branch
------
master

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

Modified Files
--------------
src/backend/storage/lmgr/predicate.c |   31 +++++++++++++++----------------
1 files changed, 15 insertions(+), 16 deletions(-)

pgsql-committers by date

Next:From: Tom LaneDate: 2012-02-29 17:11:33
Subject: pgsql: Simplify references to backslash-doubling in func.sgml.
Previous:From: Tom LaneDate: 2012-02-29 05:24:11
Subject: pgsql: Fix MSVC builds for previous patch's addition of a src/portfile

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group