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

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

From: "Gnanakumar" <gnanam(at)zoniac(dot)com>
To: "'Albe Laurenz'" <laurenz(dot)albe(at)wien(dot)gv(dot)at>, <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Very long "<IDLE> in transaction" query
Date: 2012-05-04 11:32:27
Message-ID: 008a01cd29e9$975f0cc0$c61d2640$@com (view raw or flat)
Thread:
Lists: pgsql-admin
> Then you need to identify the web server process/thread that has
> client_port open and fix the problem there.  If you get that process
> to close the transaction or terminate, your problem is solved.
> You can also terminate a database session from the server with
> the pg_terminate_backend function.

Thanks for letting me know the existence of "pg_terminate_backend(pid int)"
function.  Unfortunately, this is available only from v8.4 onwards.  We're
running v8.2.22.

> The interesting thing to know would be where in your web application
> a transaction got left open, so that it does not happen again.

Sure, we too are hunting out for the same.



In response to

pgsql-admin by date

Next:From: Thomas KellererDate: 2012-05-04 11:57:47
Subject: Getting "ident" to work in Windows
Previous:From: Albe LaurenzDate: 2012-05-04 11:08:18
Subject: Re: Very long "<IDLE> in transaction" query

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