Re: Handle infinite recursion in logical replication setup
vignesh C <vignesh21@gmail.com>
From: vignesh C <vignesh21@gmail.com>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Peter Smith <smithpb2250@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-05-05T11:14:14Z
Lists: pgsql-hackers
On Thu, May 5, 2022 at 2:41 PM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote: > > On 2022-May-04, vignesh C wrote: > > > On Mon, May 2, 2022 at 5:49 AM Peter Smith <smithpb2250@gmail.com> wrote: > > > > 1. Commit message > > > > > > In another thread using the terminology "multi-master" seems to be > > > causing some problems. Maybe you should choose different wording in > > > this commit message to avoid having the same problems? > > > > I felt, we can leave this to committer > > Please don't. See > https://postgr.es/m/20200615182235.x7lch5n6kcjq4aue@alap3.anarazel.de In this thread changing multimaster to multi-source did not get agreed and the changes did not get committed. The code still uses multimaster as in [1]. I think we should keep it as "multimaster" as that is already being used in [1]. [1] - https://www.postgresql.org/docs/current/different-replication-solutions.html Regards, Vignesh
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