Re: Handle infinite recursion in logical replication setup
Peter Smith <smithpb2250@gmail.com>
From: Peter Smith <smithpb2250@gmail.com>
To: vignesh C <vignesh21@gmail.com>
Cc: "shiy.fnst@fujitsu.com" <shiy.fnst@fujitsu.com>,
Amit Kapila <amit.kapila16@gmail.com>, Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>, "kuroda.hayato@fujitsu.com" <kuroda.hayato@fujitsu.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2022-06-28T01:58:49Z
Lists: pgsql-hackers
Here are my review comments for the v24* patch set. Now, these few comments are all trivial and non-functional. Apart from these, everything looks good to me. ======== v24-0001 ======== No comments. LGTM ======== V24-0002 ======== 2.1 doc/src/sgml/ref/create_subscription.sgml + <para> + Specifies whether the subscription will request the publisher to only + send changes that originated locally, or to send any changes + regardless of origin. Setting <literal>origin</literal> to + <literal>local</literal> means that the subscription will request the + publisher to only send changes that originated locally. Setting + <literal>origin</literal> to <literal>any</literal> means that the + publisher sends any changes regardless of their origin. The default + is <literal>any</literal>. + </para> 2.1a. IMO remove the word "any" from "any changes". Then the text will match what is written in catalogs.sgml. "send any changes regardless of origin" -> "send changes regardless of origin" (occurs 2x) 2.1b. This same text is cut/paste to the commit message so that can also be updated. ~~~ 2.2 src/backend/commands/subscriptioncmds.c + /* + * Even though "origin" parameter allows only "local" and "any" + * values, the "origin" parameter type is implemented as string + * type instead of boolean to extend the "origin" parameter to + * support filtering of origin name specified by the user in the + * later versions. + */ 2.2a. SUGGESTION Even though "origin" parameter allows only "local" and "any" values, it is implemented as a string type so that the parameter can be extended in future versions to support filtering using origin names specified by the user. 2.2b. This same text is cut/paste to the commit message so that can also be updated. ======== v24-0003 ======== 3.1 Commit message This patch does a couple of things: change 1) Checks and throws an error if 'copy_data = on' and 'origin = local' but the publication tables were also replicating from other publishers. change 2) Adds 'force' value for copy_data parameter. ~ "replicating" -> "replicated" "change 1)" -> "1)" "change 2)" -> "2)" ======== v24-0004 ======== No comments. LGTM ------ Kind Regards, Peter Smith. Fujitsu Australia
Commits
-
Improved CREATE SUBSCRIPTION message for clarity
- 1e7ca1189ccc 17.0 landed
- 842b65905046 16.0 landed
-
Fix the test case introduced by commit 8756930190.
- 032465157347 16.0 landed
-
Raise a warning if there is a possibility of data from multiple origins.
- 875693019053 16.0 landed
-
Add wait_for_subscription_sync for TAP tests.
- 0c20dd33db16 16.0 cited
-
Bump catversion for commit d8cd0c6c95c0120168df93aae095df4e0682a08a.
- 5f858dd3bebd 16.0 cited
-
Allow users to skip logical replication of data having origin.
- 366283961ac0 16.0 landed
-
Improve two comments related to a boolean DefElem's value
- 8445f5a21d40 16.0 cited
-
doc: Fix man page whitespace issues
- d7ab2a9a3c0a 15.0 cited