aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/transam/transam.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2004-08-28 21:05:26 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2004-08-28 21:05:26 +0000
commit448eb0837f7a8db270481475e8803e1e8a19a37e (patch)
treeaa9305f839a99dfec7db3d376cf30b644f2b052e /src/backend/access/transam/transam.c
parenta0a61f494dcaafe37a58cfa0c2bdab328a542f6a (diff)
downloadpostgresql-448eb0837f7a8db270481475e8803e1e8a19a37e.tar.gz
postgresql-448eb0837f7a8db270481475e8803e1e8a19a37e.zip
Rearrange order of operations in heap_drop_with_catalog and index_drop
so that we close and flush the doomed relation's relcache entry before we start to delete the underlying catalog rows, rather than afterwards. For awhile yesterday I thought that an unexpected relcache entry rebuild partway through this sequence might explain the infrequent parallel regression failures we were chasing. It doesn't, mainly because there's no CommandCounterIncrement in the sequence and so the deletions aren't "really" done yet. But it sure seems like trouble waiting to happen.
Diffstat (limited to 'src/backend/access/transam/transam.c')
0 files changed, 0 insertions, 0 deletions