aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistbuildbuffers.c
diff options
context:
space:
mode:
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>2012-02-29 15:22:49 +0200
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>2012-02-29 15:42:36 +0200
commitd6a7271958e61fe8029087a34483437292f41f6f (patch)
tree9702977c5a58323701949336036ebeebbb5188ad /src/backend/access/gist/gistbuildbuffers.c
parent8cae5810ebaaabb54171d9953bdd9cc802f0d135 (diff)
downloadpostgresql-d6a7271958e61fe8029087a34483437292f41f6f.tar.gz
postgresql-d6a7271958e61fe8029087a34483437292f41f6f.zip
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
Diffstat (limited to 'src/backend/access/gist/gistbuildbuffers.c')
0 files changed, 0 insertions, 0 deletions