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.
src/backend/storage/lmgr/predicate.c | 31 +++++++++++++++----------------
1 files changed, 15 insertions(+), 16 deletions(-)
pgsql-committers by date
|Next:||From: Tom Lane||Date: 2012-02-29 17:11:33|
|Subject: pgsql: Simplify references to backslash-doubling in func.sgml.|
|Previous:||From: Tom Lane||Date: 2012-02-29 05:24:11|
|Subject: pgsql: Fix MSVC builds for previous patch's addition of a src/portfile|