Re: Cancelling idle in transaction state

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: jd(at)commandprompt(dot)com
Cc: Simon Riggs <simon(at)2ndQuadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Cancelling idle in transaction state
Date: 2009-01-21 21:20:14
Message-ID: 200901212120.n0LLKER11791@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Joshua D. Drake wrote:
> 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

Yep, and already a TODO:

Add idle_in_transaction_timeout GUC so locks are not held for
long periods of time

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Oleg Bartunov 2009-01-21 21:29:05 Re: Pluggable Indexes
Previous Message Bruce Momjian 2009-01-21 21:18:39 Re: [Fwd: Re: Transactions and temp tables]