From 43bf7494f1d08787066165f91607a3326ec78a41 Mon Sep 17 00:00:00 2001 From: Shveta Malik Date: Wed, 18 Nov 2026 04:52:54 +0000 Subject: [PATCH v3 2/2] Doc: Explain how to recover a subscription disabled by disable_on_error If the error persists, the subscription is disabled again as soon as it is re-enabled. When the initial synchronization of a table fails because the table was dropped on the publisher or removed from the publication, ALTER SUBSCRIPTION ... REFRESH PUBLICATION is needed to remove the table from the subscription, but it can't be run on a disabled subscription. Describe how to get out of that state. --- doc/src/sgml/ref/create_subscription.sgml | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/doc/src/sgml/ref/create_subscription.sgml b/doc/src/sgml/ref/create_subscription.sgml index 6248c228a64..33b3f21eb66 100644 --- a/doc/src/sgml/ref/create_subscription.sgml +++ b/doc/src/sgml/ref/create_subscription.sgml @@ -447,6 +447,25 @@ CREATE SUBSCRIPTION subscription_namefalse. + + + If the error persists, the subscription is disabled again as soon + as it is re-enabled. For example, if initial table synchronization + fails because the table was dropped on the publisher or removed + from the publication, + ALTER SUBSCRIPTION ... REFRESH PUBLICATION + is needed to remove it from the subscription. However, this + command is not allowed while the subscription is disabled. 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. + + -- 2.34.1