| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: bug in SignalSomeChildren |
| Date: | 2010-12-20 19:07:18 |
| Message-ID: | 12829.1292872038@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Mon, Dec 20, 2010 at 1:26 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>>> Can we add a develop option to force use of the kill(0) method?
>> How will that avoid needing to have an honest answer from getppid()?
>> Without that you can't know what to issue kill() against.
> The answer to this question will probably be entirely self-evident if
> you stare at PostmasterIsAlive() for, well, it took me about 10
> seconds. So probably less than five for you.
Hmm, I was thinking that PostmasterPid was set originally from getppid,
but it looks like we rely on inheriting it through fork instead.
So maybe this will work. It's still slower and less reliable than the
getppid case for normal use, though.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2010-12-20 19:07:20 | Re: Extensions, patch v20 (bitrot fixes) |
| Previous Message | Robert Haas | 2010-12-20 19:02:03 | Re: plperlu problem with utf8 |