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

From Joshua D. Drake
Subject Re: Cancelling idle in transaction state
Date
Msg-id 1232572607.4073.22.camel@jd-laptop.pragmaticzealot.org
Whole thread Raw
In response to Re: Cancelling idle in transaction state  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Cancelling idle in transaction state  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
On Wed, 2009-01-21 at 15:46 -0500, Bruce Momjian wrote:
> Simon Riggs wrote:
> > 
> > On Wed, 2009-01-21 at 15:22 -0500, Bruce Momjian wrote:
> > > Added to TODO:
> > >     
> > >     Allow administrators to cancel multi-statement idle
> > >     transactions
> > >     
> > >         This allows locks to be released, but it is complex to report the
> > >         cancellation back to the client.
> > >     
> > >             * http://archives.postgresql.org/pgsql-hackers/2008-12/msg01340.php 
> > 
> > This is part of Hot Standby.
> > 
> > The bug is on the TODO list.
> 
> Well, if it gets done for 8.4 then we can mark it completed;  it not it
> will be there for 8.5.  The behavior is useful independent of hot
> standby.

At one time there was also a positive discussion on having something
like:

idle_in_transaction_timeout

Does this play along with that?

Joshua D.D rake


> 
> -- 
>   Bruce Momjian  <bruce@momjian.us>        http://momjian.us
>   EnterpriseDB                             http://enterprisedb.com
> 
>   + If your life is a hard drive, Christ can be your backup. +
> 
-- 
PostgreSQL - XMPP: jdrake@jabber.postgresql.org  Consulting, Development, Support, Training  503-667-4564 -
http://www.commandprompt.com/ The PostgreSQL Company, serving since 1997
 



pgsql-hackers by date:

Previous
From: "Lawrence, Ramon"
Date:
Subject: Help with Join Performance Testing
Next
From: Bruce Momjian
Date:
Subject: Re: [Fwd: Re: Transactions and temp tables]