summaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gist.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2002-01-11 20:07:03 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2002-01-11 20:07:03 +0000
commit5ab0ad5c7e70dd44d87dcdad58d9064fe10aa3e3 (patch)
treeea81f68ae1d1c445e79cd402a78a31da9bf58ff2 /src/backend/access/gist/gist.c
parenteb5e8bae26b20658422f0d75e29c46b08be3d41b (diff)
downloadpostgresql-5ab0ad5c7e70dd44d87dcdad58d9064fe10aa3e3.tar.gz
VACUUM must make sure that a HEAP_MARKED_FOR_UPDATE tuple gets marked
as either HEAP_XMAX_COMMITTED or HEAP_XMAX_INVALID once the updating transaction is gone. Otherwise some other transaction may come along and try to test the commit status of t_xmax later --- which could be after VACUUM has recycled the CLOG status for that xact. Bug introduced in post-beta4 bug fix.
Diffstat (limited to 'src/backend/access/gist/gist.c')
0 files changed, 0 insertions, 0 deletions