| From: | harrisontbooth(at)gmail(dot)com |
|---|---|
| To: | Bryan Green <dbryan(dot)green(at)gmail(dot)com> |
| Cc: | Álvaro Herrera <alvherre(at)kurilemu(dot)de>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Sutou Kouhei <kou(at)clear-code(dot)com>, michael(at)paquier(dot)xyz, robertmhaas(at)gmail(dot)com, horikyota(dot)ntt(at)gmail(dot)com, kuroda(dot)hayato(at)fujitsu(dot)com, shlok(dot)kyal(dot)oss(at)gmail(dot)com, tgl(at)sss(dot)pgh(dot)pa(dot)us |
| Subject: | Re: pg_ctl start may return 0 even if the postmaster has been already started on Windows |
| Date: | 2026-10-17 14:07:14 |
| Message-ID: | CAAH-eSX=M5fsShzL401VB7t82qiAsv2difOHnPd0qWA+HBMc-w@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Attached is a standalone refinement of Bryan's direct-launch proposal
which keeps the launched PID local & opens startup logs under the existing
restricted identity.
Native hosted x64/ARM64 LocalSystem, LocalService and elevated interactive
tests pass for spaces and U+00E9 paths. Exact ACL restoration + service
cleanup pass. Separate seeded Unicode-executable/data checks fail with both
candidate and unpatched pg_ctl controls sharing the same backend.
The mail patch applies on inspected 0d110 with tested source unchanged;
that's a static check. Does this alternative fit the intended master fix?
Best,
Harrison
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-pg-ctl-Windows-direct-start-v6.patch | text/x-patch | 9.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Previous Message | Zhijie Hou | 2026-10-17 13:44:59 | Re: [PG19] Sequence sync stops when the subscription owner can't SET ROLE to a sequence owner |