Horton

RE: Handle infinite recursion in logical replication setup

Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>

View thread View on postgr.es
From: "kuroda.hayato@fujitsu.com" <kuroda.hayato@fujitsu.com>
To: 'vignesh C' <vignesh21@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2022-03-15T04:25:21Z
Lists: pgsql-hackers 
Dear Vignesh,

> Thanks for kind explanation.
> I read above and your doc in 0002, and I put some comments.

I forgot a comment about 0002 doc.

5. create_subscription.sgml - about your example

Three possibilities were listed in the doc,
but I was not sure about b) case.
In the situation Node1 and Node2 have already become multi-master,
and data has already synced at that time.
If so, how do we realize that "there is data present only in one Node"?
Case a) and c) seem reasonable.

Best Regards,
Hayato Kuroda
FUJITSU LIMITED

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