mirror of
https://github.com/postgres/postgres.git
synced 2025-11-04 20:11:56 +03:00
Remove the NODROP SLOT option from DROP SUBSCRIPTION
It turned out this approach had problems, because a DROP command should not have any options other than CASCADE and RESTRICT. Instead, always attempt to drop the slot if there is one configured, but also add an ALTER SUBSCRIPTION action to set the slot to NONE. Author: Petr Jelinek <petr.jelinek@2ndquadrant.com> Reported-by: Tom Lane <tgl@sss.pgh.pa.us> Discussion: https://www.postgresql.org/message-id/29431.1493730652@sss.pgh.pa.us
This commit is contained in:
@@ -3393,8 +3393,8 @@ typedef struct DropSubscriptionStmt
|
||||
{
|
||||
NodeTag type;
|
||||
char *subname; /* Name of of the subscription */
|
||||
bool drop_slot; /* Should we drop the slot on remote side? */
|
||||
bool missing_ok; /* Skip error if missing? */
|
||||
DropBehavior behavior; /* RESTRICT or CASCADE behavior */
|
||||
} DropSubscriptionStmt;
|
||||
|
||||
#endif /* PARSENODES_H */
|
||||
|
||||
Reference in New Issue
Block a user