Skip site navigation (1) Skip section navigation (2)

Re: Very long "<IDLE> in transaction" query

From: "ktm(at)rice(dot)edu" <ktm(at)rice(dot)edu>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: pgsql-admin(at)postgresql(dot)org, 'Albe Laurenz' <laurenz(dot)albe(at)wien(dot)gv(dot)at>
Subject: Re: Very long "<IDLE> in transaction" query
Date: 2012-05-04 15:05:53
Message-ID: 20120504150553.GL32303@aart.rice.edu (view raw or flat)
Thread:
Lists: pgsql-admin
On Fri, May 04, 2012 at 08:57:08AM -0500, Kevin Grittner wrote:
> "ktm(at)rice(dot)edu" <ktm(at)rice(dot)edu> wrote:
>  
> > You may also want to consider setting a statement_timeout to
> > prevent this until you can find the problem with the application.
>  
> How would a statement timeout help close a transaction on an idle
> connection?  It's idle because no statements are being run.
>  
> -Kevin

Yes, you are correct. I misunderstood. Too bad we do not have a
transaction_timeout.

Regards,
Ken

In response to

pgsql-admin by date

Next:From: Craig JamesDate: 2012-05-04 16:57:43
Subject: C/C++ Linker Problem in Postgres extension functions
Previous:From: Kevin GrittnerDate: 2012-05-04 13:57:08
Subject: Re: Very long "<IDLE> in transaction" query

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group