From: Aaron Bono <postgresql@aranya.com>
To: Tomeh, Husam <htomeh@firstam.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Monitoring PostgreSQL Process
Date: Wed, 22 Nov 2006 12:46:22 -0600
Message-ID: <bf05e51c0611221046i3abdb1bcr8811a93d67ade5e0@mail.gmail.com> (raw)
In-Reply-To: <F1B0F9305B343E43A1C3EECE48B853D509308F@CITGSNA01SXCH02.ana.firstamdata.com>
References: <bf05e51c0611212149q340c54cdj8763d117ae9f43eb@mail.gmail.com>
<F1B0F9305B343E43A1C3EECE48B853D509308F@CITGSNA01SXCH02.ana.firstamdata.com>
On 11/22/06, Tomeh, Husam <htomeh@firstam.com> wrote:
>
> You may query the system view, pg_stat_activity to check out the current
> SQL statements running. To track down executed SQL statements into a
> physical log file, you may want to enable statement logging. For more
> details on that, check out:
> http://www.postgresql.org/docs/8.1/static/runtime-config-logging.html
>
> Once you capture your SQL statement, you can run "explain" on it to check
> out its execution plan.
>
I think capturing the currently running SQL will be enough for now, thanks.
It should show me what queries are running the longest and most frequently.
--
> Husam
> http://firstdba.googlepages.com
>
> ------------------------------
> *From:* pgsql-admin-owner@postgresql.org [mailto:
> pgsql-admin-owner@postgresql.org] *On Behalf Of *Aaron Bono
> *Sent:* Tuesday, November 21, 2006 9:50 PM
> *To:* pgsql-admin@postgresql.org
> *Subject:* [ADMIN] Monitoring PostgreSQL Process
>
> 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.
>
> Thanks,
> Aaron
>
> --
> ==================================================================
> Aaron Bono
> Aranya Software Technologies, Inc.
> http://www.aranya.com
> http://codeelixir.com
> ==================================================================
>
> **********************************************************************
> This message contains confidential information intended only for the use
> of the addressee(s) named above and may contain information that is legally
> privileged. If you are not the addressee, or the person responsible for
> delivering it to the addressee, you are hereby notified that reading,
> disseminating, distributing or copying this message is strictly prohibited.
> If you have received this message by mistake, please immediately notify us
> by replying to the message and delete the original message immediately
> thereafter.
>
> Thank you.
>
>
> FADLD Tag
> **********************************************************************
>
--
==================================================================
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, htomeh@firstam.com
Subject: Re: Monitoring PostgreSQL Process
In-Reply-To: <bf05e51c0611221046i3abdb1bcr8811a93d67ade5e0@mail.gmail.com>
References: <bf05e51c0611212149q340c54cdj8763d117ae9f43eb@mail.gmail.com> <F1B0F9305B343E43A1C3EECE48B853D509308F@CITGSNA01SXCH02.ana.firstamdata.com> <bf05e51c0611221046i3abdb1bcr8811a93d67ade5e0@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