Re: Monitoring a Query

From: Aaron Held <aaron(at)MetroNY(dot)com>
To: wsheldah(at)lexmark(dot)com
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-sql(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org
Subject: Re: Monitoring a Query
Date: 2002-09-20 19:13:31
Message-ID: 3D8B735B.7050206@MetroNY.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-sql

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(at)lexmark(dot)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(at)candle(dot)pha(dot)pa(dot)us>@postgresql.org on 09/20/2002
> 12:18:06 PM
>
> Sent by: pgsql-general-owner(at)postgresql(dot)org
>
>
> To: Aaron Held <aaron(at)MetroNY(dot)com>
> cc: pgsql-sql(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)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(at)postgresql(dot)org)
>>
>
>
> --
> Bruce Momjian | http://candle.pha.pa.us
> pgman(at)candle(dot)pha(dot)pa(dot)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
>
>
>

Browse pgsql-general by date

  From Date Subject
Next Message Chris Bowlby 2002-09-20 19:20:11 Re: Adjustin Priority levels..
Previous Message Steve Wolfe 2002-09-20 19:08:47 Re: PHP + PostgreSQL

Browse pgsql-sql by date

  From Date Subject
Next Message Neil Conway 2002-09-20 19:54:45 Re: Monitoring a Query
Previous Message Bruce Momjian 2002-09-20 18:56:02 Re: Monitoring a Query