You could have made the following change in your conf file and reload
the postgresql server.

log_min_duration_statement = 10000

This will help you log the queries that take more than 10000 mili
seconds to execute in your postgresql sever log file

regards
Gourish Singbal


On 5/2/05, Enrico Weigelt <weigelt(at)metux(dot)de> wrote:
> 
> Hi folks,
> 
> I'd like to find out which queries are most expensive (taking very
> long or producing high load) in a running system, to see what
> requires further optimization. (the application is quite large
> and some more folks involved, so I cant check evrything manually).
> 
> Well, the postmaster can log ev'ry single statement, but its
> really too for a human person, to read the log files.
> 
> Is there any tool for that ?
> 
> thx
> --
> ---------------------------------------------------------------------
> Enrico Weigelt    ==   metux IT service
>  phone:     +49 36207 519931         www:       http://www.metux.de/
>  fax:       +49 36207 519932         email:     contact(at)metux(dot)de
> ---------------------------------------------------------------------
>  Realtime Forex/Stock Exchange trading powered by postgresSQL :))
>                                            http://www.fxignal.net/
> ---------------------------------------------------------------------
> 
> ---------------------------(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)
> 


-- 
Best,
Gourish Singbal

In response to

• measuring most-expensive queries at 2005-05-02 03:18:30 from Enrico Weigelt

pgsql-admin by date

Next:	From: Mauri Sahlberg	Date: 2005-05-02 06:19:28
	Subject: A nightmare
Previous:	From: Ezequiel Tolnay	Date: 2005-05-02 04:52:49
	Subject: Re: pg_version_history