| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Rajeev rastogi <rajeev(dot)rastogi(at)huawei(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Dangling Client Backend Process |
| Date: | 2015-10-20 16:11:27 |
| Message-ID: | 20151020161127.GQ3391@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas wrote:
> I don't think that proc_exit(1) is the right way to exit here. It's
> not very friendly to exit without at least attempting to give the
> client a clue about what has gone wrong. I suggest something like
> this:
>
> ereport(FATAL,
> (errcode(ERRCODE_ADMIN_SHUTDOWN),
> errmsg("terminating connection due to postmaster shutdown")));
Agreed, but I don't think "shutdown" is the right word to use here --
that makes it sound like it was orderly. Perhaps "crash"?
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2015-10-20 16:51:16 | Re: Multi-column distinctness. |
| Previous Message | CharSyam | 2015-10-20 16:08:19 | [PATCH] Typos in comments |