Re: Handle infinite recursion in logical replication setup

vignesh C <vignesh21@gmail.com>

From: vignesh C <vignesh21@gmail.com>

To: Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>

Cc: Amit Kapila <amit.kapila16@gmail.com>, "kuroda.hayato@fujitsu.com" <kuroda.hayato@fujitsu.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2022-04-05T01:54:37Z

Lists: pgsql-hackers

On Mon, Apr 4, 2022 at 6:50 PM Ashutosh Bapat
<ashutosh.bapat.oss@gmail.com> wrote:
>
> I didn't find this in https://commitfest.postgresql.org/37/. Is this
> somewhere in the commitfest?

I missed adding it earlier, I have added it to commitfest today:
https://commitfest.postgresql.org/38/3610/

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