Re: Terminate the idle sessions
От | Tom Lane |
---|---|
Тема | Re: Terminate the idle sessions |
Дата | |
Msg-id | 728355.1610312336@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Terminate the idle sessions (Thomas Munro <thomas.munro@gmail.com>) |
Ответы |
RE: Terminate the idle sessions
|
Список | pgsql-hackers |
Thomas Munro <thomas.munro@gmail.com> writes: > On Thu, Jan 7, 2021 at 4:51 PM Tom Lane <tgl@sss.pgh.pa.us> wrote: >> Thomas Munro <thomas.munro@gmail.com> writes: >>> One of the strange things about these errors is that they're >>> asynchronous/unsolicited, but they appear to the client to be the >>> response to their next request (if it doesn't eat ECONNRESET instead). >> Right, which is what makes class 57 (operator intervention) seem >> attractive to me. From the client's standpoint these look little >> different from ERRCODE_ADMIN_SHUTDOWN or ERRCODE_CRASH_SHUTDOWN, >> which are in that category. > Yeah, that's a good argument. Given the lack of commentary on this thread, I'm guessing that people aren't so excited about this topic that a change in the existing sqlstate assignment for ERRCODE_IDLE_IN_TRANSACTION_SESSION_TIMEOUT would fly. So I propose to change the new ERRCODE_IDLE_SESSION_TIMEOUT to be in class 57 and call it good. regards, tom lane
В списке pgsql-hackers по дате отправления: