On Fri, 2026-06-19 at 11:40 -0700, Jeff Davis wrote: > * add an escape hatch for users to turn off tablesync slots so that > DROP will always succeed
It looks like SLOT_NAME=NONE is already supposed to be this escape hatch, even for tablesync slots. From the docs: "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." https://www.postgresql.org/docs/devel/sql-dropsubscription.html But DropSubscription() only does the early-return if there are no tablesync slots. If there are tablesync slots, it still tries to contact the publisher, even if SLOT_NAME=NONE. > * consider it an unimportant edge case and leave it the way it is > (with 0001 & 0002 already done), and close the open item I plan to close this open item, and treat the above as a pre-existing bug, which may require a backport. Regards, Jeff Davis
