aboutsummaryrefslogtreecommitdiff
path: root/src/backend/commands/cluster.c
diff options
context:
space:
mode:
authorRobert Haas <rhaas@postgresql.org>2012-01-26 09:24:54 -0500
committerRobert Haas <rhaas@postgresql.org>2012-01-26 09:30:27 -0500
commit0e549697d1c6b8eeb623c497dc38a5aed4deea1e (patch)
treed1b6063331a7ff56f061e35d45523776c04680d8 /src/backend/commands/cluster.c
parentbc3347484a7bf9eddb98e4352d84599cae9a31c6 (diff)
downloadpostgresql-0e549697d1c6b8eeb623c497dc38a5aed4deea1e.tar.gz
postgresql-0e549697d1c6b8eeb623c497dc38a5aed4deea1e.zip
Classify DROP operations by whether or not they are user-initiated.
This doesn't do anything useful just yet, but is intended as supporting infrastructure for allowing sepgsql to sensibly check DROP permissions. KaiGai Kohei and Robert Haas
Diffstat (limited to 'src/backend/commands/cluster.c')
-rw-r--r--src/backend/commands/cluster.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/commands/cluster.c b/src/backend/commands/cluster.c
index 9408f259a61..349d13034e3 100644
--- a/src/backend/commands/cluster.c
+++ b/src/backend/commands/cluster.c
@@ -1443,7 +1443,7 @@ finish_heap_swap(Oid OIDOldHeap, Oid OIDNewHeap,
* The new relation is local to our transaction and we know nothing
* depends on it, so DROP_RESTRICT should be OK.
*/
- performDeletion(&object, DROP_RESTRICT);
+ performDeletion(&object, DROP_RESTRICT, PERFORM_DELETION_INTERNAL);
/* performDeletion does CommandCounterIncrement at end */