From: Gnanakumar <gnanam@zoniac.com>
To: 'Albe Laurenz' <laurenz.albe@wien.gv.at>
To: pgsql-admin@postgresql.org
Subject: Re: Very long "<IDLE> in transaction" query
Date: Fri, 4 May 2012 17:02:27 +0530
Message-ID: <008a01cd29e9$975f0cc0$c61d2640$@com> (raw)
In-Reply-To: <D960CB61B694CF459DCFB4B0128514C207D5026B@exadv11.host.magwien.gv.at>
References: <008101cd2916$1c023b20$5406b160$@com>
<D960CB61B694CF459DCFB4B0128514C207D4FFA7@exadv11.host.magwien.gv.at>
<008001cd29db$ab24ba60$016e2f20$@com>
<D960CB61B694CF459DCFB4B0128514C207D5026B@exadv11.host.magwien.gv.at>
> 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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: gnanam@zoniac.com, laurenz.albe@wien.gv.at
Subject: Re: Very long "<IDLE> in transaction" query
In-Reply-To: <008a01cd29e9$975f0cc0$c61d2640$@com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox