Re: Lock timeouts and unusual spikes in replication lag with logical parallel transaction streaming - Mailing list pgsql-bugs

From Amit Kapila
Subject Re: Lock timeouts and unusual spikes in replication lag with logical parallel transaction streaming
Date
Msg-id CAA4eK1JzNuYYSJxohoV3xmEeLS8b4wPu14kp4_Wc5wiC4WdVoA@mail.gmail.com
Whole thread Raw
In response to Re: Lock timeouts and unusual spikes in replication lag with logical parallel transaction streaming  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-bugs
On Mon, Sep 22, 2025 at 2:06 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
>
> On Thu, Sep 18, 2025 at 9:47 AM Zane Duffield <duffieldzane@gmail.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
thedefault. 
> >
> >> 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
thelog probably would have made it easier to work this whole problem out, though, so I hope someone else can test out
thechange 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.



pgsql-bugs by date:

Previous
From: "sunw.fnst"
Date:
Subject: The issue of incorrect width estimation in UNION queries
Next
From: Etsuro Fujita
Date:
Subject: Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c