| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Chris Travers <chris(at)metatrontech(dot)com>, Cristian Bittel <cbittel(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [BUGS] BUG #5305: Postgres service stops when closing Windows session |
| Date: | 2010-08-24 13:58:52 |
| Message-ID: | 28002.1282658332@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Robert Haas wrote:
>> Yeah, that seems very plausible, although exactly how to verify I don't know.
> And here is confirmation from the Microsoft web site:
> In some instances, calling GetExitCode() against the failed process
> indicates the following exit code:
> 128L ERROR_WAIT_NO_CHILDREN - There are no child processes to wait for.
Given the existence of the deadman switch mechanism (which I hadn't
remembered when this thread started), I'm coming around to the idea that
we could just treat exit(128) as nonfatal on Windows. If for some
reason the child hadn't died instantly at startup, the deadman switch
would distinguish that from the case described here.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2010-08-24 14:02:41 | Re: [BUGS] BUG #5305: Postgres service stops when closing Windows session |
| Previous Message | Bruce Momjian | 2010-08-24 13:43:00 | Re: [BUGS] BUG #5305: Postgres service stops when closing Windows session |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2010-08-24 14:02:41 | Re: [BUGS] BUG #5305: Postgres service stops when closing Windows session |
| Previous Message | Bruce Momjian | 2010-08-24 13:43:00 | Re: [BUGS] BUG #5305: Postgres service stops when closing Windows session |