From: Aaron Bono <postgresql@aranya.com>
To: adey <adey11@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Monitoring PostgreSQL Process
Date: Wed, 22 Nov 2006 20:33:28 -0600
Message-ID: <bf05e51c0611221833t1ffb48bal6dbbac8398ee946f@mail.gmail.com> (raw)
In-Reply-To: <1c66bda80611221602w4a2766a1l3dff7b05eedac574@mail.gmail.com>
References: <bf05e51c0611212149q340c54cdj8763d117ae9f43eb@mail.gmail.com>
<1c66bda80611221602w4a2766a1l3dff7b05eedac574@mail.gmail.com>
I queried pg_stat_activity a bunch of times and was able to tell what tables
were being queried. I finally honed in on the section of code causing the
problem and fix it and all is good on the server now - over 90% idle.
I think the reason some of the processes were showing high CPU usage was
that they are not reporting real time usage but some kind of average. My
guess is that some of the processes that showed high usage were not the
sources of the CPU problems I was currently having.
Thanks all.
On 11/22/06, adey <adey11@gmail.com> wrote:
>
> The following query with the stats_command_string parameter turned on will
> give you some of the SQL per transaction:-
>
>
> SELECT
> datid,
> datname as "DB Name",
> substr(procpid,1,6) as "Procpid",
> substr(usesysid,1,5) as "UseSysid",
> usename,
> current_query as "SQL",
> query_start
> FROM
> pg_stat_activity
> order by
> procpid;
>
>
> On 11/22/06, Aaron Bono <postgresql@aranya.com> wrote:
> >
> > I have a couple processes/connections to one of our databases that
> > appears to be eating up most of the CPU and we are trying to determine what
> > these processes are doing that is taking so much CPU time.
> >
> > Is there a way to monitor the SQL being run for a specific
> > connection/process?
> >
> > We are using PostgreSQL 8.1.5 on CentOS Linux.
> >
> >
--
==================================================================
Aaron Bono
Aranya Software Technologies, Inc.
http://www.aranya.comhttp://codeelixir.com
==================================================================
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: postgresql@aranya.com, adey11@gmail.com
Subject: Re: Monitoring PostgreSQL Process
In-Reply-To: <bf05e51c0611221833t1ffb48bal6dbbac8398ee946f@mail.gmail.com>
References: <bf05e51c0611212149q340c54cdj8763d117ae9f43eb@mail.gmail.com> <1c66bda80611221602w4a2766a1l3dff7b05eedac574@mail.gmail.com> <bf05e51c0611221833t1ffb48bal6dbbac8398ee946f@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox