Re: Cancelling idle in transaction state - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Cancelling idle in transaction state
Date
Msg-id 1262275125.19367.11248.camel@ebony
Whole thread Raw
In response to Re: Cancelling idle in transaction state  (Joachim Wieland <joe@mcknight.de>)
Responses Re: Cancelling idle in transaction state
List 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



pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: Serializable Isolation without blocking
Next
From: "David E. Wheeler"
Date:
Subject: Re: PATCH: Add hstore_to_json()