Hi, On Wed, Oct 7, 2026 at 2:48 PM vignesh C <[email protected]> wrote: > > On Tue, 6 Oct 2026 at 12:07, Hayato Kuroda (Fujitsu) > <[email protected]> wrote: > > > > Hi Vignesh, > > > > > I was planning to review this patch set and noticed the patch does not > > > apply anymore, could you post a rebased version for reviewing? > > > > Thanks for the contact. Here is an updated version. > > I ran into a reliability issue in pa_send_data() > (src/backend/replication/logical/applyparallelworker.c). > pa_send_data() retries shm_mq_send() for SHM_SEND_TIMEOUT_MS(9) > seconds when the parallel apply worker is slow to consume its input. > If it still cannot send the data, it returns false. All its callers in > worker.c treat this as a hard error and terminate the apply worker: > ereport(ERROR, ..., > errmsg("could not send data to the logical replication " > "parallel apply worker"));
Thanks for reporting. This is a known behavior that has been there since the introduction of streaming parallel mode. It was considered complicated to add a new deadlock detector for this timeout case, so it wasn't deemed worth the effort. And it would be rare to trigger this in production, and we haven't received any reports of this kind of timeout yet, so I think this isn't a issue. Since this is an existing behavior, and the new parallel apply is actually harder to hit this because we're parallelizing non-streamed transactions which tend to be small, I think we should consider it independently rather than doing something in the current patches. Best Regards, Zhijie Hou
