| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Archiver not exiting upon crash |
| Date: | 2012-05-23 16:12:26 |
| Message-ID: | 1337789546.23660.1.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On mån, 2012-05-21 at 12:52 -0400, Tom Lane wrote:
> I see Peter's commit d6de43099ac0bddb4b1da40088487616da892164 only
> touched postgres.c's quickdie(), and not all the *other* background
> processes with identical coding. That seems a clear oversight, so I
> will go fix it.
None[*] of the other signal handlers call elog/ereport, which was the
cause of the original problem. It might still be good to review this
across the board, though.
* - for some value of "none", I didn't check all of them in detail
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2012-05-23 16:13:52 | Re: Archiver not exiting upon crash |
| Previous Message | Merlin Moncure | 2012-05-23 15:47:44 | Re: Why is indexonlyscan so darned slow? |