From 1da5c119594e4fb07fb6a2c57f66642fa5e966fb Mon Sep 17 00:00:00 2001
From: Robert Haas <rhaas@postgresql.org>
Date: Thu, 15 Dec 2011 19:02:58 -0500
Subject: Improve behavior of concurrent ALTER <relation> .. SET SCHEMA.

If the referrent of a name changes while we're waiting for the lock,
we must recheck permissons.  We also now check the relkind before
locking, since it's easy to do that long the way.

Patch by me; review by Noah Misch.
---
 src/backend/commands/alter.c | 1 -
 1 file changed, 1 deletion(-)

(limited to 'src/backend/commands/alter.c')

diff --git a/src/backend/commands/alter.c b/src/backend/commands/alter.c
index 2954bb27dd9..8513837fa10 100644
--- a/src/backend/commands/alter.c
+++ b/src/backend/commands/alter.c
@@ -191,7 +191,6 @@ ExecAlterObjectSchemaStmt(AlterObjectSchemaStmt *stmt)
 		case OBJECT_TABLE:
 		case OBJECT_VIEW:
 		case OBJECT_FOREIGN_TABLE:
-			CheckRelationOwnership(stmt->relation, true);
 			AlterTableNamespace(stmt->relation, stmt->newschema,
 								stmt->objectType, AccessExclusiveLock);
 			break;
-- 
cgit v1.2.3