| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Marko Tiikkaja <marko(at)joh(dot)to> |
| Cc: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Change pg_cancel_*() to ignore current backend |
| Date: | 2015-05-19 23:30:13 |
| Message-ID: | CAKFQuwZPi0jjyYsuXf+Oy6rv8H3pO03L2GAM+mtUGFcfHt_2Rw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, May 19, 2015 at 4:23 PM, Marko Tiikkaja <marko(at)joh(dot)to> wrote:
> On 2015-05-20 00:59, Jim Nasby wrote:
>
>> I find it annoying to have to specifically exclude pg_backend_pid() from
>> pg_stat_activity if I'm trying to kill a bunch of backends at once, and
>> I can't think of any reason why you'd ever want to call a pg_cancel_*
>> function with your own PID.
>>
>
> That's a rather easy way of testing that you're handling FATAL errors
> correctly from a driver/whatever.
>
>
I'm having trouble thinking of a PC name for the function we create that
should do this; while changing the pg_cancel_* functions to operate more
safely.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2015-05-19 23:38:32 | Re: jsonb concatenate operator's semantics seem questionable |
| Previous Message | Marko Tiikkaja | 2015-05-19 23:23:13 | Re: Change pg_cancel_*() to ignore current backend |