Re: Cancelling idle in transaction state

Simon Riggs <simon@2ndquadrant.com>

From: Simon Riggs <simon@2ndQuadrant.com>
To: Joachim Wieland <joe@mcknight.de>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Hannu Krosing <hannu@2ndquadrant.com>, James Pye <lists@jwp.name>, pgsql-hackers <pgsql-hackers@postgresql.org>, Kris Jurka <books@ejurka.com>
Date: 2009-12-31T15:58:45Z
Lists: pgsql-hackers
On Thu, 2009-12-31 at 15:41 +0100, Joachim Wieland wrote:

> I still think that we should have three transaction cancel modes, one
> to cancel an idle transaction, another one to cancel a running query
> and a third one that just cancels the transaction regardless of it
> being idle or not. This last one is what you are implementing now, and
> it is what HS wants to do. 

pg_cancel_backend() is currently conditional on whether a statement is
active or not, so should really be called pg_cancel_if_active(). What
people want is an unconditional way to stop a transaction. I don't see
the need for 3 modes (and that has nothing to do with HS).

-- 
 Simon Riggs           www.2ndQuadrant.com