| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 16:27:47 |
| Message-ID: | AANLkTinOqsTHhktV7SykgRo7E1eTSsFxHJpEx73oU29=@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Dec 20, 2010 at 8:20 AM, Alvaro Herrera
<alvherre(at)commandprompt(dot)com> wrote:
> Excerpts from Robert Haas's message of vie dic 17 14:08:04 -0300 2010:
>
>> I'm having a bit of trouble confirming this on MacOS X, though.
>> 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.
>
> Yeah, this problem has been known for some time and causes quite some
> pain. We have an open problem report on autovacuum failing to run after
> some time, and we haven't been able to get a backtrace or strace because
> of this issue -- trying to attach to it causes a full system restart
> (PostmasterIsAlive returns false, autovac launcher dies, this death
> causes postmaster to shut everything down and restart). This is on
> FreeBSD.
Can we add a develop option to force use of the kill(0) method?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2010-12-20 16:31:23 | Re: Binary timestamp with without timezone |
| Previous Message | Robert Haas | 2010-12-20 16:27:05 | Re: Extensions and custom_variable_classes |