summaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistxlog.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2012-11-26 15:55:43 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2012-11-26 15:55:43 -0500
commit532994299e2ff208a58376134fab75f5ae471e41 (patch)
tree640a22d6172d9dbdccf88ecc1195c6a23a3b0a8c /src/backend/access/gist/gistxlog.c
parentd3237e04ca380d6c08f6133fde97a9d956e3161a (diff)
downloadpostgresql-532994299e2ff208a58376134fab75f5ae471e41.tar.gz
Revert patch for taking fewer snapshots.
This reverts commit d573e239f03506920938bf0be56c868d9c3416da, "Take fewer snapshots". While that seemed like a good idea at the time, it caused execution to use a snapshot that had been acquired before locking any of the tables mentioned in the query. This created user-visible anomalies that were not present in any prior release of Postgres, as reported by Tomas Vondra. While this whole area could do with a redesign (since there are related cases that have anomalies anyway), it doesn't seem likely that any future patch would be reasonably back-patchable; and we don't want 9.2 to exhibit a behavior that's subtly unlike either past or future releases. Hence, revert to prior code while we rethink the problem.
Diffstat (limited to 'src/backend/access/gist/gistxlog.c')
0 files changed, 0 insertions, 0 deletions