| From: | Zane Duffield <duffieldzane(at)gmail(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(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-18 04:17:09 |
| Message-ID: | CACMiCkUJ6Pb7P4MdRB8g-YksXAgypZ7ZRYUHQ9u7nU-WiTxsLg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2025-09-18 04:19:46 | Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos |
| Previous Message | Tom Lane | 2025-09-18 04:11:00 | Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos |