| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, 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:38:51 |
| Message-ID: | 9664.1432168731@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2015-05-21 00:46:51 | Re: Change pg_cancel_*() to ignore current backend |
| Previous Message | Jim Nasby | 2015-05-21 00:34:31 | Re: Disabling trust/ident authentication configure option |