On Wed, Feb 3, 2016 at 5:36 PM, Jim Nasby <jim.na...@bluetreble.com> wrote:
>> I think killing the session is a perfectly sensible thing to do in this
>> case. Everything meaningful that was done in the session will be rolled
>> back - no need to waste resources keeping the connection open.
> Except you end up losing stuff like every GUC you've set, existing temp
> tables, etc. For an application that presumably doesn't matter, but for a
> user connection it would be a PITA.
> I wouldn't put a bunch of effort into it though. Dropping the connection is
> certainly better than nothing.
Well, my view is that if somebody wants an alternative behavior
besides dropping the connection, they can write a patch to provide
that as an additional option. That, too, has been discussed before.
But the fact that somebody might want that doesn't make this a bad or
useless behavior. Indeed, I'd venture that more people would want
this than would want that.
The Enterprise PostgreSQL Company
Sent via pgsql-hackers mailing list (email@example.com)
To make changes to your subscription: