Re: SIGUSR1 pingpong between master na autovacum launcher causes crash

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SIGUSR1 pingpong between master na autovacum launcher causes crash
Date: 2009-08-24 18:47:42
Message-ID: 20090824184741.GF5962@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> > Tom Lane wrote:
> >> Yeah, I added that recently to try to detect postmaster children
> >> that exit without cleaning up properly. I seem to have missed this
> >> error case :-(. Actually it looks like fork failure for regular
> >> backends gets it wrong too :-( :-( --- would you please also add one
> >> in the pid<0 path in BackendStartup? I think this logic is in 8.4
> >> too, in which case it'll need to be back-patched.
>
> > And this one too.
>
> Almost right --- we only want to release for non-dead_end children.
> I fixed that part.

Oops, sorry about that -- I even noticed it :-(

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2009-08-24 18:51:28 Re: hba load error and silent mode
Previous Message Greg Stark 2009-08-24 18:37:33 Re: Slaying the HYPOTamus