Horton

Re: Handle infinite recursion in logical replication setup

Peter Smith <smithpb2250@gmail.com>

View thread View on postgr.es
From: Peter Smith <smithpb2250@gmail.com>
To: "kuroda.hayato@fujitsu.com" <kuroda.hayato@fujitsu.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, vignesh C <vignesh21@gmail.com>
Date: 2022-03-07T06:20:03Z
Lists: pgsql-hackers 
On Mon, Mar 7, 2022 at 5:12 PM kuroda.hayato@fujitsu.com
<kuroda.hayato@fujitsu.com> wrote:
>
> Dear Peter,
>
> > > So, why does the patch use syntax option 1?
>
> IMU it might be useful for the following case.
>
> Assuming that multi-master configuration with node1, node2.
> Node1 has a publication pub1 and a subscription sub2, node2 has pub2 and sub1.
>
> From that situation, please consider that new node node3 is added
> that subscribe some changes from node2.
>
> If the feature is introduced as option1, new publication must be defined in node2.
> If that is introduced as option2, however, maybe pub2 can be reused.
> i.e. multiple declaration of publications can be avoided.
>

Yes. Thanks for the example. I had the same observation in my last post  [1]

------
[1] https://www.postgresql.org/message-id/CAHut%2BPtRxiQR_4UFLNThg-NNRV447FvwtcR-BvqMzjyMJXKwfw%40mail.gmail.com

Kind Regards,
Peter Smith
Fujitsu Australia.

Commits

  1. Improved CREATE SUBSCRIPTION message for clarity

  2. Fix the test case introduced by commit 8756930190.

  3. Raise a warning if there is a possibility of data from multiple origins.

  4. Add wait_for_subscription_sync for TAP tests.

  5. Bump catversion for commit d8cd0c6c95c0120168df93aae095df4e0682a08a.

  6. Allow users to skip logical replication of data having origin.

  7. Improve two comments related to a boolean DefElem's value

  8. doc: Fix man page whitespace issues