Horton

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

Zane Duffield <duffieldzane@gmail.com>

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

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 your help Amit, Hou-san, and Hayato-san.

Zane