Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load

Amit Kapila <amit.kapila16@gmail.com>

From: Amit Kapila <amit.kapila16@gmail.com>

To: Shlok Kyal <shlok.kyal.oss@gmail.com>

Cc: vignesh C <vignesh21@gmail.com>, Euler Taveira <euler@eulerto.com>, duffieldzane@gmail.com, pgsql-bugs@lists.postgresql.org

Date: 2025-07-24T10:49:02Z

Lists: pgsql-bugs

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Fix duplicate transaction replay during pg_createsubscriber.
- e1c3654839e4 19 (unreleased) landed
- 33f74b806ce3 18.0 landed
- 967309116f0d 17.6 landed
pg_createsubscriber: Fix an unpredictable recovery wait time.
- 03b08c8f5f3e 18.0 cited

On Wed, Jul 23, 2025 at 6:56 PM Shlok Kyal <shlok.kyal.oss@gmail.com> wrote:
>
> >
> Thanks for reviewing the patch. I have added comments and attached the
> updated patch.
> v6_HEAD applies to HEAD and REL_18_STABLE. v6_REL_17 applies to REL_17_STABLE.
>

Thanks, I have pushed the fix after changing the comments.

-- 
With Regards,
Amit Kapila.