From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, Noah Misch <noah(at)leadboat(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_ctl/pg_rewind tests vs. slow AIX buildfarm members |
Date: | 2015-09-03 20:07:19 |
Message-ID: | 32333.1441310839@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> There is no equivalent of execl, nor a cmd.exe exquivalent of the
> shell's exec. But surely the equivalent of the fork/execl you're doing
> here would be a simple CreateProcess(). I don't see why you need a shell
> in the middle on Windows at all.
The problem is to get the output redirection to work. I imagine it could
be rewritten without involving the shell, but it'd be less than trivial
(or at least, I'm not going to do it).
If we did get that to work, it could probably be applied to the
service-start case as well, which currently just does a CreateProcess and
pays no attention to what happens to postmaster stderr.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2015-09-03 20:14:02 | Re: On-demand running query plans using auto_explain and signals |
Previous Message | Pavel Stehule | 2015-09-03 20:06:59 | Re: On-demand running query plans using auto_explain and signals |