| 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 18:26:46 |
| Message-ID: | 12099.1292869606@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:
>>> Attaching gdb to either the startup process or a WAL sender causes
>>> PostmasterIsAlive to return false, resulting in a near-immediate exit.
>>> Seems pretty stupid for attaching gdb to change the return value of
>>> getppid() but it seems like that must be what's happening.
> 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.
Seems like the correct path here is to complain to gdb and/or BSD
upstreams about this misbehavior.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-12-20 18:43:57 | Re: bug in SignalSomeChildren |
| Previous Message | Magnus Hagander | 2010-12-20 18:25:21 | Re: MingW and MiniDumps |