Re: Dangling Client Backend Process
От | Robert Haas |
---|---|
Тема | Re: Dangling Client Backend Process |
Дата | |
Msg-id | CA+TgmoYxMqLqZWFRoD++YCr7WZv=nADu8TZ96uavjX9nEDs2Ag@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Dangling Client Backend Process (Alvaro Herrera <alvherre@2ndquadrant.com>) |
Ответы |
Re: Dangling Client Backend Process
Re: Dangling Client Backend Process |
Список | pgsql-hackers |
On Tue, Oct 20, 2015 at 12:11 PM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote: > 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"? Well, that's a little speculative. "due to unexpected postmaster exit"? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: