From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de>, Noah Misch <noah(at)leadboat(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_ctl/pg_rewind tests vs. slow AIX buildfarm members |
Date: | 2015-09-03 19:31:06 |
Message-ID: | 31376.1441308666@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
>> I'don't like adding a couple seconds of test runtime for the benefit of
>> very slow platforms.
> Me either. This is the first time I've seen an indication that the
> start_postmaster change mentioned in the comment is actually important
> for production use, rather than just being cleanup. I think we ought
> to just fix it. I'm willing to take care of the Unix side if someone
> will explain how to change the Windows side.
Attached is a draft patch for this. I think it's fine for Unix (unless
someone wants to object to relying on "/bin/sh -c"), but I have no idea
whether it works for Windows. The main risk is that if CMD.EXE runs
the postmaster as a subprocess rather than overlaying itself a la shell
"exec", the PID we'd get back would apply only to CMD.EXE not to the
eventual postmaster. If so, I do not know how to fix that, or whether
it's fixable at all.
Note that this makes the test case in question fail reliably, which is
reasonable behavior IMO so I just changed the test.
If this does (or can be made to) work on Windows, I'd propose applying
it back to 9.2, where the current coding came in.
regards, tom lane
Attachment | Content-Type | Size |
---|---|---|
fork-exec-in-pg_ctl.patch | text/x-diff | 12.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2015-09-03 19:34:36 | Re: PG_CATCH used without PG_RETHROW |
Previous Message | Greg Stark | 2015-09-03 19:12:04 | PG_CATCH used without PG_RETHROW |