| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
| 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 21:47:25 |
| Message-ID: | 20170.1340401645@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> writes:
>>> PID PENDING CAUGHT IGNORED BLOCKED COMMAND
>>> 12480 20004004 34084005 c942b002 fffefeff postgres: writer process
>>> 9841 20004004 34084007 c942b000 fffefeff postgres: wal writer process
> this seems to be SIGUSR1,SIGTERM and SIGQUIT
OK, I looked up OpenBSD's signal numbers on the web. It looks to me
like these two processes have everything blocked except KILL and STOP
(which are unblockable of course). I do not see any place in the PG
code that could possibly set such a mask (note that BlockSig should
have more holes in it than that). So I'm thinking these must be
blocked inside some system function that's installed a restrictive
signal mask, or some such function forgot to restore the mask on exit.
Could you gdb each of these processes and get a stack trace?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-06-22 21:53:16 | Re: random failing builds on spoonbill - backends not exiting... |
| Previous Message | Stefan Kaltenbrunner | 2012-06-22 21:19:57 | Re: random failing builds on spoonbill - backends not exiting... |