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 09:52:47
Message-ID: 008001cd29db$ab24ba60$016e2f20$@com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

> SELECT application_name, client_addr, client_hostname, client_port
> FROM pg_stat_activity
> WHERE procpid = 14740;

> (Replace 14740 of the process ID of the "idle in transaction" backend).

> Look on the client machine and find the process that holds TCP port
> "client_port" open (on Linux you can use "lsof" for that).

Ours is a web-based application and all calls are made "only" from where the
web server is running. No external calls are allowed in my case. Hence,
the "only" client machine in my case is the web server.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Albe Laurenz 2012-05-04 11:08:18 Re: Very long "<IDLE> in transaction" query
Previous Message Kevin Grittner 2012-05-03 17:54:25 Re: DELETE and UPDATE triggers on parent table of partioned table not firing.