DROP SUBSCRIPTION(7)     PostgreSQL 18.6 Documentation    DROP SUBSCRIPTION(7)

NAME
       DROP_SUBSCRIPTION - remove a subscription

SYNOPSIS
       DROP SUBSCRIPTION [ IF EXISTS ] name [ CASCADE | RESTRICT ]

DESCRIPTION
       DROP SUBSCRIPTION removes a subscription from the database cluster.

       To execute this command the user must be the owner of the subscription.

       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 not attempt to drop the subscription's own replication slot. It
       may still connect to the publisher to drop internally-created table
       synchronization slots if some table synchronization is left unfinished;
       if the publisher is unreachable, those slots (and the main slot, if it
       still exists) must be dropped manually. Otherwise it/they will continue
       to reserve WAL and might eventually cause the disk to fill up. See also
       Section 29.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)), ALTER SUBSCRIPTION
       (ALTER_SUBSCRIPTION(7))

PostgreSQL 18.6                      2026                 DROP SUBSCRIPTION(7)