| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Rajeev rastogi <rajeev(dot)rastogi(at)huawei(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, 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-30 14:57:45 |
| Message-ID: | 12267.1446217065@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> writes:
> adding a parseInput(conn) into the loop yields the expected
> FATAL: 57P01: terminating connection due to unexpected postmaster exit
> Is there really any reason not to do that?
Might work, but it probably needs some study:
(a) is it safe
(b) is this the right place / are there other places
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2015-10-30 15:03:29 | Re: Dangling Client Backend Process |
| Previous Message | Michael Paquier | 2015-10-30 14:48:25 | Re: WIP: Fix parallel workers connection bug in pg_dump (Bug #13727) |