Re: Lock timeouts and unusual spikes in replication lag with logical parallel transaction streaming

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Zane Duffield <duffieldzane(at)gmail(dot)com>
Cc: "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: Lock timeouts and unusual spikes in replication lag with logical parallel transaction streaming
Date: 2025-09-24 08:34:12
Message-ID: CAA4eK1JzNuYYSJxohoV3xmEeLS8b4wPu14kp4_Wc5wiC4WdVoA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Sep 22, 2025 at 2:06 PM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>
> On Thu, Sep 18, 2025 at 9:47 AM Zane Duffield <duffieldzane(at)gmail(dot)com> wrote:
> >
> > Sorry for the late reply.
> >
> > After some more testing, we are going ahead with `streaming = parallel`, with the change to reset `lock_timeout` to the default.
> >
> >> No, as per my understanding it is because parallel apply worker
> >> exiting due to lock_timeout set in the test. Ideally, the patch
> >> proposed by Kuroda-San should show in LOGs that the parallel worker is
> >> exiting due to lock_timeout. Can you try that once?
> >
> >
> > I don't think I'll have time to compile a patched version and run the tests again, sorry. Have this information in the log probably would have made it easier to work this whole problem out, though, so I hope someone else can test out the change and get it merged.
> >
>
> Thanks for the feedback. I'll take care of this once the release
> freeze for 18 is over.
>

Pushed.

--
With Regards,
Amit Kapila.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Etsuro Fujita 2025-09-24 10:28:02 Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
Previous Message sunw.fnst 2025-09-24 06:13:32 The issue of incorrect width estimation in UNION queries