| From: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
|---|---|
| To: | 'Alexander Lakhin' <exclusion(at)gmail(dot)com> |
| Cc: | "'pgsql-hackers(at)lists(dot)postgresql(dot)org'" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | RE: 030_pg_recvlogical fails because the same PID is assigned |
| Date: | 2026-07-31 09:12:00 |
| Message-ID: | OS9PR01MB1214958718280AE9FC6CB4550F5C82@OS9PR01MB12149.jpnprd01.prod.outlook.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dear Alexander,
> Thank you for paying attention to the failure!
>
> FWIW, it reminded me of [1], so reused PIDs on Windows caused us problems
> before -- probably if we could somehow force Windows to reuse PIDs more
> often, it would help discover other similar anomalies.
According to my googling, on linux /proc/sys/kernel/ns_last_pid can be used to
control the PID which is assigned for the next process, but I don't think it a
robust way. And quite unclear for the Windows ;-(.
BTW, here is a patch to fix the issue.
Best regards,
Hayato Kuroda
FUJITSU LIMITED
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Make-030_pg_recvlogical-robust.patch | application/octet-stream | 1.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2026-07-31 09:25:33 | Re: sequencesync worker race with REFRESH SEQUENCES |
| Previous Message | Anthonin Bonnefoy | 2026-07-31 09:00:54 | Add PQTRACE env to enable protocol tracing in libpq |