aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistget.c
diff options
context:
space:
mode:
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>2014-07-29 10:33:15 +0300
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>2014-07-29 11:59:22 +0300
commite74e0906fad5fcdcc807d4655cdc69dded5d58f2 (patch)
tree169ee9b2e572d20fda67922bdd41e84adc31913d /src/backend/access/gist/gistget.c
parent61e48efba579682f75332688bdb89f9eee24fb63 (diff)
downloadpostgresql-e74e0906fad5fcdcc807d4655cdc69dded5d58f2.tar.gz
postgresql-e74e0906fad5fcdcc807d4655cdc69dded5d58f2.zip
Treat 2PC commit/abort the same as regular xacts in recovery.
There were several oversights in recovery code where COMMIT/ABORT PREPARED records were ignored: * pg_last_xact_replay_timestamp() (wasn't updated for 2PC commits) * recovery_min_apply_delay (2PC commits were applied immediately) * recovery_target_xid (recovery would not stop if the XID used 2PC) The first of those was reported by Sergiy Zuban in bug #11032, analyzed by Tom Lane and Andres Freund. The bug was always there, but was masked before commit d19bd29f07aef9e508ff047d128a4046cc8bc1e2, because COMMIT PREPARED always created an extra regular transaction that was WAL-logged. Backpatch to all supported versions (older versions didn't have all the features and therefore didn't have all of the above bugs).
Diffstat (limited to 'src/backend/access/gist/gistget.c')
0 files changed, 0 insertions, 0 deletions