aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistscan.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2011-02-15 15:50:17 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2011-02-15 15:50:17 -0500
commit69bef7ff79eb33e8a355e79e7fbb5338d1557775 (patch)
tree87be2a9d3e53cf0662f8e443e2b27eee1b6c954f /src/backend/access/gist/gistscan.c
parent13a9a7b55b4ced1ac017a3ca5a10f600d242a27a (diff)
downloadpostgresql-69bef7ff79eb33e8a355e79e7fbb5338d1557775.tar.gz
postgresql-69bef7ff79eb33e8a355e79e7fbb5338d1557775.zip
Add CheckTableNotInUse calls in DROP TABLE and DROP INDEX.
Recent releases had a check on rel->rd_refcnt in heap_drop_with_catalog, but failed to cover the possibility of pending trigger events at DROP time. (Before 8.4 we didn't even check the refcnt.) When the trigger events were eventually fired, you'd get "could not open relation with OID nnn" errors, as in recent report from strk. Better to throw a suitable error when the DROP is attempted. Also add a similar check in DROP INDEX. Back-patch to all supported branches.
Diffstat (limited to 'src/backend/access/gist/gistscan.c')
0 files changed, 0 insertions, 0 deletions