From 293913568e6a7a86fd1479e1cff8e2ecb58d6568 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sat, 13 Apr 2024 15:44:03 +0200 Subject: Adding upstream version 16.2. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/sql-dropsubscription.html | 49 +++++++++++++++++++++++++++++ 1 file changed, 49 insertions(+) create mode 100644 doc/src/sgml/html/sql-dropsubscription.html (limited to 'doc/src/sgml/html/sql-dropsubscription.html') diff --git a/doc/src/sgml/html/sql-dropsubscription.html b/doc/src/sgml/html/sql-dropsubscription.html new file mode 100644 index 0000000..b83d4b7 --- /dev/null +++ b/doc/src/sgml/html/sql-dropsubscription.html @@ -0,0 +1,49 @@ + +DROP SUBSCRIPTION

DROP SUBSCRIPTION

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

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. +

\ No newline at end of file -- cgit v1.2.3