| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Jon Nelson <jnelson+pgsql(at)jamponi(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, "david(dot)g(dot)johnston(at)gmail(dot)com >> David G Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Subject: | Re: Change pg_cancel_*() to ignore current backend |
| Date: | 2015-05-21 00:27:52 |
| Message-ID: | 555D2688.5060302@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2015-05-21 00:34:31 | Re: Disabling trust/ident authentication configure option |
| Previous Message | Jim Nasby | 2015-05-21 00:22:04 | Re: RFC: Non-user-resettable SET SESSION AUTHORISATION |