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

Поиск
Список
Период
Сортировка
Искать
От
Gnanakumar
Тема
Re: Very long "<IDLE> in transaction" query
Дата
в 06:54:36
Msg-id
008001cd29db$ab24ba60$016e2f20$@com
Ответ на
Список
Дерево обсуждения
Very long "<IDLE> in transaction" query "Gnanakumar" <gnanam@zoniac.com>
Re: Very long "<IDLE> in transaction" query Thomas Markus <t.markus@proventis.net>
Re: Very long "<IDLE> in transaction" query Jan Lentfer <Jan.Lentfer@web.de>
Re: Very long "<IDLE> in transaction" query "Albe Laurenz" <laurenz.albe@wien.gv.at>
Re: Very long "<IDLE> in transaction" query "Gnanakumar" <gnanam@zoniac.com>
Re: Very long "<IDLE> in transaction" query "ktm@rice.edu" <ktm@rice.edu>
Re: Very long "<IDLE> in transaction" query "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: Very long "<IDLE> in transaction" query "ktm@rice.edu" <ktm@rice.edu>
Re: Very long "<IDLE> in transaction" query "Albe Laurenz" <laurenz.albe@wien.gv.at>
Re: Very long "<IDLE> in transaction" query "Gnanakumar" <gnanam@zoniac.com>
> 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.


В списке pgsql-admin по дате отправления
От: Kevin Grittner
Дата:
От: Albe Laurenz
Дата:
FAQ