Re: Very long " in transaction" query
От | ktm@rice.edu |
---|---|
Тема | Re: Very long " |
Дата | |
Msg-id | 20120504133842.GH32303@aart.rice.edu обсуждение исходный текст |
Ответ на |
Re: Very long " |
Ответы |
Re: Very long " |
Список | pgsql-admin |
On Fri, May 04, 2012 at 03:22:47PM +0530, Gnanakumar wrote: > > 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. > You may also want to consider setting a statement_timeout to prevent this until you can find the problem with the application. Regards, Ken
В списке pgsql-admin по дате отправления: