From: | Peter Smith <smithpb2250(at)gmail(dot)com> |
---|---|
To: | vignesh C <vignesh21(at)gmail(dot)com> |
Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: PGDOCS - add more links in the pub/sub reference pages |
Date: | 2023-10-11 00:31:02 |
Message-ID: | CAHut+PscejpR5iqOJgcZLnzjk7MQfMkeGXWkUN+c2REhsoQN8A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Oct 10, 2023 at 5:10 PM vignesh C <vignesh21(at)gmail(dot)com> wrote:
>
> Few more instances in other logical replication related pages:
> 1) Another instance was in alter_subscription.sgml:
> Fetch missing table information from publisher. This will start
> replication of tables that were added to the subscribed-to publications
> since <command>CREATE SUBSCRIPTION</command> or
> the last invocation of <command>REFRESH PUBLICATION</command>.
OK, modified in v4.
> 2) Few more instances were in logical-replication-subscription.html
> 2.a) Normally, the remote replication slot is created automatically when the
> subscription is created using <command>CREATE SUBSCRIPTION</command> and it
> is dropped automatically when the subscription is dropped using
> <command>DROP SUBSCRIPTION</command>. In some situations, however, it can
> be useful or necessary to manipulate the subscription and the underlying
> replication slot separately.
> 2.b) When dropping a subscription, the remote host is not reachable. In
> that case, disassociate the slot from the subscription
> using <command>ALTER SUBSCRIPTION</command> before attempting to drop
> the subscription.
The above were in section "31.2.1 Replication Slot Management". OK,
modified in v4.
> 2.c) If a subscription is affected by this problem, the only way to resume
> replication is to adjust one of the column lists on the publication
> side so that they all match; and then either recreate the subscription,
> or use <literal>ALTER SUBSCRIPTION ... DROP PUBLICATION</literal> to
> remove one of the offending publications and add it again.
The above was in section "31.2.1 Replication Slot Management". OK,
modified in v4.
> 2.d) The
> transaction that produced the conflict can be skipped by using
> <command>ALTER SUBSCRIPTION ... SKIP</command> with the finish LSN
> (i.e., LSN 0/14C0378).
> 2.e) Before using this function, the subscription needs to be
> disabled temporarily
> either by <command>ALTER SUBSCRIPTION ... DISABLE</command> or,
>
The above was in the section "31.5 Conflicts". OK, modified in v4.
~~
Thanks for reporting those. PSA v4.
======
Kind Regards,
Peter Smith.
Fujitsu Australia
Attachment | Content-Type | Size |
---|---|---|
v4-0001-Add-more-pub-sub-links.patch | application/octet-stream | 11.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2023-10-11 00:54:34 | Re: broken master regress tests |
Previous Message | Peter Smith | 2023-10-11 00:28:16 | Re: PGDOCS - add more links in the pub/sub reference pages |