| From: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
|---|---|
| To: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Subject: | Re: WaitEventSetWaitBlock() can still hang on Windows due to connection reset |
| Date: | 2025-04-17 19:00:00 |
| Message-ID: | 37baa757-0659-4e55-8c46-1e3d15236d21@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dear Kuroda-san,
17.04.2025 10:10, Hayato Kuroda (Fujitsu) wrote:
> Dear Alexander,
>
> While analyzing the BF failure [1], I noticed that the same issue may happen here,
> which means apply worker waited something. According to the log, apply worker (PID 2820)
> stucked so that logical replication could not restart.
>
> ...
>
> Now the report has been reported for both physical and logical replication,
> but I suspected that this can happen for all the application.
>
> [1]:https://buildfarm.postgresql.org/cgi-bin/show_stage_log.pl?nm=drongo&dt=2025-04-12%2003%3A59%3A38&stg=recovery-check
Thank you for the analysis!
I think you're right, it's the same issue, so I've added the link to the
wiki page.
Best regards,
Alexander Lakhin
Neon (https://neon.tech)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nico Williams | 2025-04-17 19:14:37 | Re: Giving the shared catalogues a defined encoding |
| Previous Message | Andrew Dunstan | 2025-04-17 18:37:55 | Re: disabled SSL log_like tests |