Re: Change pg_cancel_*() to ignore current backend - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Change pg_cancel_*() to ignore current backend
Date
Msg-id 9664.1432168731@sss.pgh.pa.us
Whole thread Raw
In response to Re: Change pg_cancel_*() to ignore current backend  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Responses Re: Change pg_cancel_*() to ignore current backend  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
Jim Nasby <Jim.Nasby@BlueTreble.com> writes:
> On 5/20/15 6:56 PM, Andres Freund wrote:
>> On 2015-05-20 18:48:59 -0500, Jim Nasby wrote:
>>> and generally if you want to terminate the connection there's easier
>>> ways to do that then "SELECT pg_terminate_backend(pg_backend_pid())".

>> Which would be what exactly? Say, you're inside a security definer
>> function.

> Error isn't good enough so you want to kill the backend? I hadn't 
> considered that; what's the common use case for it? ISTM it'd be better 
> to allow elog to log and then terminate the backend, but of course that 
> doesn't help with backwards compatibility. :/

That's spelled elog(FATAL), no?
        regards, tom lane



pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: Disabling trust/ident authentication configure option
Next
From: Andres Freund
Date:
Subject: Re: Change pg_cancel_*() to ignore current backend