Re: recovery is stuck when children are not processing SIGQUIT from previous crash

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Marko Kreen <markokr(at)gmail(dot)com>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-admin(at)postgresql(dot)org
Subject: Re: recovery is stuck when children are not processing SIGQUIT from previous crash
Date: 2009-11-12 15:24:45
Message-ID: 24621.1258039485@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-hackers

Marko Kreen <markokr(at)gmail(dot)com> writes:
> On 11/12/09, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> The other thought is that quickdie should block signals before
>> starting to do anything.

> There would still be possibility of recursive syslog() calls.
> Shouldn't we fix that too?

That's what the signal block would do.

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Marko Kreen 2009-11-12 15:34:53 Re: recovery is stuck when children are not processing SIGQUIT from previous crash
Previous Message Marko Kreen 2009-11-12 15:01:40 Re: recovery is stuck when children are not processing SIGQUIT from previous crash

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2009-11-12 15:28:57 Re: PL/Python array support
Previous Message Joshua Tolley 2009-11-12 15:21:29 Re: plperl and inline functions -- first draft