From: Aaron Held <aaron@MetroNY.com>
To: wsheldah@lexmark.com
Cc: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: pgsql-sql@postgresql.org
Cc: pgsql-general@postgresql.org
Subject: Re: Monitoring a Query
Date: Fri, 20 Sep 2002 15:13:31 -0400
Message-ID: <3D8B735B.7050206@MetroNY.com> (raw)
References: <OFFB5F6014.73E8A50B-ON85256C3A.00673363@lexmark.com>
There are some good views and functions you can use to get at the SQL
query being executed
try turning on the stats collector and running
select * from pg_stat_activity;
(See http://www.postgresql.org/idocs/index.php?monitoring-stats.html )
You can also see the procID.
From Python I can use this info to get a lot of details about the
running query, CPU and memory use.
But I can't tell how far along it actually is.
-Aaron
wsheldah@lexmark.com wrote:
> I just downloaded and installed pgmonitor on my dev. machine after seeing
> your post, and it looks nifty. Only problem is I really want to avoid
> running X on the database server to conserve the RAM it uses, and this
> appears to require X. Any terminal applications to monitor database
> activity, perhaps loosely analagous to mtop for MySQL?
> (http://mtop.sf.net/)
>
> Wes Sheldahl
>
>
>
>
> Bruce Momjian <pgman@candle.pha.pa.us>@postgresql.org on 09/20/2002
> 12:18:06 PM
>
> Sent by: pgsql-general-owner@postgresql.org
>
>
> To: Aaron Held <aaron@MetroNY.com>
> cc: pgsql-sql@postgresql.org, pgsql-general@postgresql.org
> Subject: Re: [GENERAL] Monitoring a Query
>
>
>
> There is pgmonitor:
>
> http://gborg.postgresql.org/project/pgmonitor
>
> ---------------------------------------------------------------------------
>
> Aaron Held wrote:
>
>>Is there any way to monitor a long running query?
>>
>>I have stats turned on and I can see my queries, but is there any better
>>measure of the progress?
>>
>>Thanks,
>>-Aaron Held
>>
>>select current_query from pg_stat_activity;
>>current_query
>>
>><IDLE>
>><IDLE>
>><IDLE>
>><IDLE>
>><IDLE> in transaction
>>FETCH ALL FROM PgSQL_470AEE94
>><IDLE> in transaction
>>select * from "Calls" WHERE "DurationOfCall" = 2.5 AND "DateOfCall" =
>>'7/01/02' AND ("GroupCode" = 'MIAMI' OR "GroupCode" = 'Salt Lake');
>><IDLE>
>><IDLE>
>><IDLE>
>>
>>
>>---------------------------(end of broadcast)---------------------------
>>TIP 2: you can get off all lists at once with the unregister command
>> (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>>
>
>
> --
> Bruce Momjian | http://candle.pha.pa.us
> pgman@candle.pha.pa.us | (610) 359-1001
> + If your life is a hard drive, | 13 Roberts Road
> + Christ can be your backup. | Newtown Square, Pennsylvania
> 19073
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
>
>
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 using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: aaron@MetroNY.com, wsheldah@lexmark.com, pgman@candle.pha.pa.us, pgsql-general@postgresql.org
Subject: Re: Monitoring a Query
In-Reply-To: <3D8B735B.7050206@MetroNY.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