Re: Change pg_cancel_*() to ignore current backend

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. :/

What do people think about pg_cancel_query() and pg_terminate_session()?
-- 
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com