Postgres Pro
Downloads
Home   >   mailing lists

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

From Jim Nasby
Subject Re: Change pg_cancel_*() to ignore current backend
Date
Msg-id 555F9676.6030206@BlueTreble.com
Whole thread Raw
In response to Re: Change pg_cancel_*() to ignore current backend  (Eric Ridge <e_ridge@tcdi.com>)
Responses Re: Change pg_cancel_*() to ignore current backend  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Change pg_cancel_*() to ignore current backend  (Eric Ridge <eebbrr@gmail.com>)
List pgsql-hackers
Tree view 
On 5/22/15 3:08 PM, Eric Ridge wrote:
>> I find it annoying to have to specifically exclude pg_backend_pid() from pg_stat_activity if I'm trying to kill a
bunchof backends at once, and I can't think of any reason why you'd ever want to call a pg_cancel_* function with your
ownPID.
 
> I'm just a lurker, but regularly get bitten by this exact thing.
>
> Rather than change the behavior of pg_cancel/terminate_backend(), why not change pg_stat_activity to exclude the
currentsession?  Seems like showing a row in pg_stat_activity for "SELECT * FROM pg_stat_activity" is kinda useless
anyways.

Interesting idea. I suspect that would be even more invasive than 
modifying the functions though...
-- 
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com

pgsql-hackers by date:

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