From af731dd77e8c9f2f933043d35f87895255a4fb9a Mon Sep 17 00:00:00 2001 From: Shveta Malik Date: Wed, 18 Nov 2026 04:52:54 +0000 Subject: [PATCH v4 2/2] Doc: Explain how to recover a subscription disabled by disable_on_error If the underlying cause of an error is not resolved, a subscription disabled by disable_on_error is disabled again shortly after it is re-enabled. For example, initial table synchronization keeps failing when the table or the publication was dropped on the publisher, or the table was removed from the publication. ALTER SUBSCRIPTION ... REFRESH PUBLICATION is needed to remove such a table from the subscription, but it can't be run on a disabled subscription, so the user can be left stuck. Update the docs to mention a way out of this. --- doc/src/sgml/ref/alter_subscription.sgml | 20 ++++++++++++++++++++ doc/src/sgml/ref/create_subscription.sgml | 12 ++++++++++++ 2 files changed, 32 insertions(+) diff --git a/doc/src/sgml/ref/alter_subscription.sgml b/doc/src/sgml/ref/alter_subscription.sgml index 545264e8a0a..e819adac921 100644 --- a/doc/src/sgml/ref/alter_subscription.sgml +++ b/doc/src/sgml/ref/alter_subscription.sgml @@ -185,6 +185,26 @@ ALTER SUBSCRIPTION name RENAME TO < that are still part of the publication. + + + This command cannot be run while the subscription is disabled. If the + subscription was disabled by + disable_on_error + because initial table synchronization keeps failing, for example + because the table or the publication was dropped on the publisher, or + the table was removed from the publication, this command is needed to + remove the table from the subscription. To resolve this, either fix + the cause on the publisher before re-enabling the subscription, or + temporarily set + disable_on_error to false, + re-enable the subscription using + ALTER SUBSCRIPTION ... ENABLE, + run ALTER SUBSCRIPTION ... REFRESH PUBLICATION, and + then set disable_on_error back to + true. + + + refresh_option specifies additional options for the refresh operation. The supported options are: diff --git a/doc/src/sgml/ref/create_subscription.sgml b/doc/src/sgml/ref/create_subscription.sgml index 92552e97009..ccf1f0b10b5 100644 --- a/doc/src/sgml/ref/create_subscription.sgml +++ b/doc/src/sgml/ref/create_subscription.sgml @@ -469,6 +469,18 @@ CREATE SUBSCRIPTION subscription_namefalse. + + + If the underlying cause is not resolved, the subscription is + disabled again shortly after it is re-enabled. For example, if + initial table synchronization fails because the table or the + publication was dropped on the publisher, or the table was removed + from the publication, the same error recurs each time the + subscription is re-enabled. See + ALTER SUBSCRIPTION ... REFRESH PUBLICATION + for how to resolve this. + + -- 2.34.1