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

From Tom Lane
Subject Re: Change pg_cancel_*() to ignore current backend
Date
Msg-id 13917.1432331463@sss.pgh.pa.us
Whole thread Raw
In response to Re: Change pg_cancel_*() to ignore current backend  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Responses Re: Change pg_cancel_*() to ignore current backend  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers
Jim Nasby <Jim.Nasby@BlueTreble.com> writes:
> On 5/22/15 3:08 PM, Eric Ridge wrote:
>> 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...

-1 ... some other columns in pg_stat_activity are potentially useful even
for the current session, eg session and transaction start times.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Asynchronous DRAM Self-Refresh
Next
From: Tom Lane
Date:
Subject: Re: jsonb concatenate operator's semantics seem questionable