Postgres Pro
Downloads
Home   >   mailing lists

Re: recovery is stuck when children are not processing SIGQUIT from previous crash - Mailing list pgsql-admin

From Marko Kreen
Subject Re: recovery is stuck when children are not processing SIGQUIT from previous crash
Date
Msg-id e51f66da0911120701k48eb0ffare76e7d26ca71690c@mail.gmail.com
Whole thread Raw
In response to Re: recovery is stuck when children are not processing SIGQUIT from previous crash  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: recovery is stuck when children are not processing SIGQUIT from previous crash  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-admin
Tree view 
On 11/12/09, Tom Lane <tgl@sss.pgh.pa.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?

I'm not sure how exactly.  If the recursive elog() must stay, then
perhaps simple 'volatile int' around syslog() ?

--
marko

pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: recovery is stuck when children are not processing SIGQUIT from previous crash
Next
From: Tom Lane
Date:
Subject: Re: recovery is stuck when children are not processing SIGQUIT from previous crash