Search Postgresql Archives

Re: <IDLE> connections and cpu consumption

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 11/09/11 11:35 AM, Gauthier, Dave wrote:
Ahhhh... so if the script that has the connection open would only terminate the transaction, then vacuum wouldn't get behind?

I actually made a change in that script to rollback when the script doesn't need the changes in the transaction, hopefully allowing vacuum to do its thing.

(from memory, I might have details wrong here)...

select now()-xact_start as "Transaction Age", usename, datname, procpid, application_name from pg_stat_activity where current_query='<IDLE> in transaction" order by 1 desc;

that will list the age of those idle-in-transactions, oldest on top.

--
john r pierce                            N 37, W 122
santa cruz ca                         mid-left coast


--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux