Skip site navigation (1) Skip section navigation (2)

Re: [ANNOUNCE] pgtop, display PostgreSQL processes in `top' style

From: Jeff - <threshar(at)torgo(dot)978(dot)org>
To: Markus Schaber <schabi(at)logix-tt(dot)com>
Cc: Cosimo Streppone <cosimo(at)streppone(dot)it>,pgsql-announce(at)postgresql(dot)org, pgsql-sql(at)postgresql(dot)org
Subject: Re: [ANNOUNCE] pgtop, display PostgreSQL processes in `top' style
Date: 2005-05-04 14:28:19
Message-ID: 8721B090-C082-4860-88F3-CBD60EE4D4D0@torgo.978.org (view raw or flat)
Thread:
Lists: pgsql-announcepgsql-sql
On May 2, 2005, at 6:09 PM, Markus Schaber wrote:
>
>> 1) is it possible to know Pg backend uptime with
>>    SQL queries? Or must I look at postmaster.pid file?
>>    or even something else?
>>
>
> In contrib, there's a function caled backend_pid() defined in
> misc_utils.sql, it may be helpful for you.
>
> markus
>

I wrote a small util called "pgtop" that does a top style listing on  
PG in terms of cpu. I also have one called pgiomonitor (that is on  
pgfoundry and mostly done) that does the same but shows you which  
tables are producing the most IO)

http://postgresql.jefftrout.com/pgtop.pl

it only runs on linux and it must run on the same box as pg itself.
You may want to look at it and see if you can get anything good out  
of it.

queries / second is tricky.  You could look at my pgspy utility but  
it is in C.  It can give you queries / second data
--
Jeff Trout <jeff(at)jefftrout(dot)com>
http://www.jefftrout.com/
http://www.stuarthamm.net/





In response to

pgsql-announce by date

Next:From: Greg Sabino MullaneDate: 2005-05-04 23:44:18
Subject: Re: [ANNOUNCE] IMPORTANT: two new PostgreSQL security problems found
Previous:From: Michelle KonzackDate: 2005-05-03 12:56:14
Subject: Re: REMOVE

pgsql-sql by date

Next:From: Mischa SandbergDate: 2005-05-04 19:27:35
Subject: HELP: aggregating insert rule for multirow inserts.
Previous:From: Markus SchaberDate: 2005-05-04 14:19:02
Subject: Re: all server processes terminated; reinitializing

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group