Re: "unexpected EOF" messages
От | Tom Lane |
---|---|
Тема | Re: "unexpected EOF" messages |
Дата | |
Msg-id | 27799.1336065641@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: "unexpected EOF" messages ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>) |
Ответы |
Re: "unexpected EOF" messages
|
Список | pgsql-hackers |
"Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes: > Would it make sense to use 08003 (connection_does_not_exist) when a > broken connection for an idle process is discovered, and 08006 > (connection_failure) for the "in transaction" failure? What about a > failure just after COMMIT and before successfully sending that > result to the client? I notice there's a SQLSTATE 08007 > (transaction_resolution_unknown), but I don't know whether that > makes sense on the server side, or just on the client side. AFAICS, all the 08 class is meant to be issued by client-side code, not the server. I think we probably have to use nonstandard SQLSTATEs for these messages. regards, tom lane
В списке pgsql-hackers по дате отправления: