bdr: lift restriction on ALTER .. RENAME
authorAlvaro Herrera <alvherre@alvh.no-ip.org>
Tue, 8 Apr 2014 21:00:10 +0000 (18:00 -0300)
committerAndres Freund <andres@anarazel.de>
Thu, 3 Jul 2014 15:55:24 +0000 (17:55 +0200)
contrib/bdr/bdr_commandfilter.c

index c413506f1060eaa8aa05df3979df5951f7d6256a..4d08dec9f7ddb7ddd7440ca6ab9860c1c6036d1b 100644 (file)
@@ -77,7 +77,6 @@ bdr_commandfilter(Node *parsetree,
 {
    int         severity = ERROR;
    ListCell   *cell;
-   RenameStmt *renameStatement;
    AlterTableStmt *alterTableStatement;
    bool hasInvalid;
 
@@ -137,19 +136,6 @@ bdr_commandfilter(Node *parsetree,
                                       severity, alterTableStatement->missing_ok);
            break;
 
-       case T_RenameStmt:
-           renameStatement = (RenameStmt *) parsetree;
-           if (renameStatement->renameType == OBJECT_TABLE ||
-               renameStatement->renameType == OBJECT_TYPE ||
-               renameStatement->renameType == OBJECT_ATTRIBUTE)
-           {
-               error_on_persistent_rv(renameStatement->relation,
-                                      "ALTER ... RENAME",
-                                      AccessExclusiveLock, severity,
-                                      renameStatement->missing_ok);
-           }
-           break;
-
        case T_AlterEnumStmt:
            ereport(severity,
             (errmsg("ALTER TYPE ... ADD VALUE is unsafe with BDR active")));