| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Juan José Santamaría Flecha <juanjo(dot)santamaria(at)gmail(dot)com> |
| Cc: | cilizili(at)protonmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #16080: pg_ctl is failed if a fake cmd.exe exist in the current directory. |
| Date: | 2019-10-26 15:20:04 |
| Message-ID: | 26128.1572103204@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
=?UTF-8?Q?Juan_Jos=C3=A9_Santamar=C3=ADa_Flecha?= <juanjo(dot)santamaria(at)gmail(dot)com> writes:
> There is a difference in the behaviour for the WIN32 port. In other
> platforms execl() is called from "src/bin/pg_ctl/pc_ctl" with the full path
> ("/bin/sh"), but for WIN32 the function CreateProcessAsUser() calls the CMD
> command without a path, and this function has a search logic of its own [1].
Right, but does cmd.exe have a well-defined location in Windows?
I don't think we can know which drive it's on, for starters.
Ultimately this seems like a problem of insecure search path,
which is not our responsibility to fix (and people would not
appreciate us trying, in many cases).
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Juan José Santamaría Flecha | 2019-10-26 17:33:02 | Re: BUG #16080: pg_ctl is failed if a fake cmd.exe exist in the current directory. |
| Previous Message | Juan José Santamaría Flecha | 2019-10-26 14:15:04 | Re: BUG #16080: pg_ctl is failed if a fake cmd.exe exist in the current directory. |