Re: Dangling Client Backend Process
От | Andres Freund |
---|---|
Тема | Re: Dangling Client Backend Process |
Дата | |
Msg-id | 20151030150329.GC6677@alap3.anarazel.de обсуждение исходный текст |
Ответ на | Re: Dangling Client Backend Process (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Dangling Client Backend Process
Re: Dangling Client Backend Process |
Список | pgsql-hackers |
On 2015-10-30 10:57:45 -0400, Tom Lane wrote: > Andres Freund <andres@anarazel.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: Yea, definitely. I was just at pgconf.eu's keynote catching up on a talk. No fully thought through proposal's to be expected ;) > (a) is it safe I don't immediately see why not. > (b) is this the right place / are there other places I think it's ok for the send failure case, in a quick lookthrough I didn't find anything else for writes - I'm not entirely sure all read cases are handled tho, but it seems less likely to be mishandles. Greetings, Andres Freund
В списке pgsql-hackers по дате отправления: