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

From: Zane Duffield <duffieldzane(at)gmail(dot)com>
To: vignesh C <vignesh21(at)gmail(dot)com>
Cc: Shlok Kyal <shlok(dot)kyal(dot)oss(at)gmail(dot)com>, Euler Taveira <euler(at)eulerto(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load
Date: 2025-04-29 00:09:40
Message-ID: CACMiCkW8_3RdjTw07Ds_REMHXH-6-GCvTO2M5Thy=Y8rHyydZw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Apr 28, 2025 at 2:58 PM vignesh C <vignesh21(at)gmail(dot)com> wrote:

> As an alternative, we could set recovery_target_inclusive to false in
> the setup_recovery function. This way, recovery would stop just before
> the recovery target, allowing the publisher to start replicating
> exactly from the consistent point.
> Thoughts?

This sounds to me like a simpler and more correct solution.

Thanks,
Zane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Pavel Stehule 2025-04-29 05:00:58 Re: Postgres 17.4 is much slower than Postgres 15.12 using RECURSIVE
Previous Message marcos sicat 2025-04-28 21:53:26 Re: Postgres 17.4 is much slower than Postgres 15.12 using RECURSIVE