Re: connections and cpu consumption - Mailing list pgsql-general

From Gauthier, Dave
Subject Re: connections and cpu consumption
Date
Msg-id 482E80323A35A54498B8B70FF2B8798004D5DE1706@azsmsx504.amr.corp.intel.com
Whole thread Raw
In response to Re: connections and cpu consumption  (John R Pierce <pierce@hogranch.com>)
List pgsql-general
ALas, there is no "application_name" column in that table.  But I do like the "now()-xact_start" !

-----Original Message-----
From: pgsql-general-owner@postgresql.org [mailto:pgsql-general-owner@postgresql.org] On Behalf Of John R Pierce
Sent: Wednesday, November 09, 2011 2:58 PM
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] <IDLE> connections and cpu consumption

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,
hopefullyallowing 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@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

pgsql-general by date:

Previous
From: Guillaume Lelarge
Date:
Subject: Re: Insufficient privilege when initiating backup
Next
From: hubert depesz lubaczewski
Date:
Subject: Why does autovacuum run in so small blocks?