Horton

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

Amit Kapila <amit.kapila16@gmail.com>

View thread
From: Amit Kapila <amit.kapila16@gmail.com>
To: Zane Duffield <duffieldzane@gmail.com>
Cc: "Zhijie Hou (Fujitsu)" <houzj.fnst@fujitsu.com>, "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Date: 2025-09-24T08:34:12Z
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 →

  1. Fix LOCK_TIMEOUT handling during parallel apply.

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 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.