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

From David G. Johnston
Subject Re: Change pg_cancel_*() to ignore current backend
Date
Msg-id CAKFQuwZPi0jjyYsuXf+Oy6rv8H3pO03L2GAM+mtUGFcfHt_2Rw@mail.gmail.com
Whole thread Raw
In response to Re: Change pg_cancel_*() to ignore current backend  (Marko Tiikkaja <marko@joh.to>)
Responses Re: Change pg_cancel_*() to ignore current backend  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers
On Tue, May 19, 2015 at 4:23 PM, Marko Tiikkaja <marko@joh.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.​
 

pgsql-hackers by date:

Previous
From: Marko Tiikkaja
Date:
Subject: Re: Change pg_cancel_*() to ignore current backend
Next
From: Jim Nasby
Date:
Subject: Re: jsonb concatenate operator's semantics seem questionable