| From: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: random failing builds on spoonbill - backends not exiting... |
| Date: | 2012-06-22 20:42:02 |
| Message-ID: | 4FE4D89A.8020002@kaltenbrunner.cc |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 06/22/2012 09:39 PM, Tom Lane wrote:
> Andres Freund <andres(at)2ndquadrant(dot)com> writes:
>> On Friday, June 22, 2012 08:51:55 PM Robert Haas wrote:
>>> I remarked to Stefan that the symptoms seem consistent with the idea
>>> that the children have signals blocked. But I don't know how that
>>> could happen.
>
>> You cannot block sigkill.
>
> sigterm is at issue, not sigkill. But I don't care for the
> signals-blocked theory either, at least not in three different children
> at the same time.
>
> (Hey Stefan, is there a way on BSD to check a process's signals-blocked
> state from outside? If so, next time this happens you should try to
> determine the children's signal state.)
with help from RhodiumToad on IRC:
# ps -o pid,sig,sigcatch,sigignore,sigmask,command -p 12480
PID PENDING CAUGHT IGNORED BLOCKED COMMAND
12480 20004004 34084005 c942b002 fffefeff postgres: writer process
(postgres)
# ps -o pid,sig,sigcatch,sigignore,sigmask,command -p 9841
PID PENDING CAUGHT IGNORED BLOCKED COMMAND
9841 20004004 34084007 c942b000 fffefeff postgres: wal writer process
(postgres)
Stefan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-06-22 20:43:17 | Re: pg_dump and dependencies and --section ... it's a mess |
| Previous Message | Dimitri Fontaine | 2012-06-22 20:22:54 | Re: pg_prewarm |