# DROP_SUBSCRIPTION(7) - man - phpman

DROP [SUBSCRIPTION(7)](https://www.chedong.com/phpMan.php/man/SUBSCRIPTION/7/markdown)               PostgreSQL 14.23 Documentation               DROP [SUBSCRIPTION(7)](https://www.chedong.com/phpMan.php/man/SUBSCRIPTION/7/markdown)



## NAME
       DROP_SUBSCRIPTION - remove a subscription

## SYNOPSIS
       DROP SUBSCRIPTION [ IF EXISTS ] _name_ [ CASCADE | RESTRICT ]

## DESCRIPTION
       **DROP** **SUBSCRIPTION** removes a subscription from the database cluster.

       A subscription can only be dropped by a superuser.

       **DROP** **SUBSCRIPTION** cannot be executed inside a transaction block if the subscription is
       associated with a replication slot. (You can use **ALTER** **SUBSCRIPTION** to unset the slot.)

## PARAMETERS
       IF EXISTS
           Do not throw an error if the subscription does not exist. A notice is issued in this
           case.

       _name_
           The name of a subscription to be dropped.

       CASCADE
       RESTRICT
           These key words do not have any effect, since there are no dependencies on subscriptions.

## NOTES
       When dropping a subscription that is associated with a replication slot on the remote host
       (the normal state), **DROP** **SUBSCRIPTION** will connect to the remote host and try to drop the
       replication slot (and any remaining table synchronization slots) as part of its operation.
       This is necessary so that the resources allocated for the subscription on the remote host are
       released. If this fails, either because the remote host is not reachable or because the
       remote replication slot cannot be dropped or does not exist or never existed, the **DROP**
       **SUBSCRIPTION** command will fail. To proceed in this situation, first disable the subscription
       by executing ALTER SUBSCRIPTION ... DISABLE, and then disassociate it from the replication
       slot by executing ALTER SUBSCRIPTION ... SET (slot_name = NONE). After that, **DROP**
       **SUBSCRIPTION** will no longer attempt any actions on a remote host. Note that if the remote
       replication slot still exists, it (and any related table synchronization slots) should then
       be dropped manually; otherwise it/they will continue to reserve WAL and might eventually
       cause the disk to fill up. See also Section 31.2.1.

       If a subscription is associated with a replication slot, then **DROP** **SUBSCRIPTION** cannot be
       executed inside a transaction block.

## EXAMPLES
       Drop a subscription:

           DROP SUBSCRIPTION mysub;

## COMPATIBILITY
       **DROP** **SUBSCRIPTION** is a PostgreSQL extension.

## SEE ALSO
       CREATE SUBSCRIPTION (**CREATE**___**[SUBSCRIPTION**(7)](https://www.chedong.com/phpMan.php/man/SUBSCRIPTION/7/markdown)), ALTER SUBSCRIPTION (**ALTER**___**[SUBSCRIPTION**(7)](https://www.chedong.com/phpMan.php/man/SUBSCRIPTION/7/markdown))



PostgreSQL 14.23                                2026                            DROP [SUBSCRIPTION(7)](https://www.chedong.com/phpMan.php/man/SUBSCRIPTION/7/markdown)