Re: Terminate the idle sessions - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: Terminate the idle sessions
Date
Msg-id CA+hUKG++BE=w-P9JzS0SkTRpmcDctSjafk6JZ5+6QxoZurPkzQ@mail.gmail.com
Whole thread Raw
In response to Re: Terminate the idle sessions  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Terminate the idle sessions  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
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.



pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: plpgsql variable assignment with union is broken
Next
From: Craig Ringer
Date:
Subject: Re: [PATCH] Runtime control of CLOBBER_CACHE_ALWAYS