| From: | Richard Huxton <dev(at)archonet(dot)com> |
|---|---|
| To: | Ulrich Wisser <ulrich(dot)wisser(at)relevanttraffic(dot)se> |
| Cc: | pgsql-performance(at)postgresql(dot)org, bruno(at)wolff(dot)to |
| Subject: | Re: [GENERAL] How to know which queries are to be optimised? |
| Date: | 2004-08-12 11:16:20 |
| Message-ID: | 411B5184.6090106@archonet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-performance |
Ulrich Wisser wrote:
>> You can log queries that run for at least a specified amount of time.
>> This will be useful in finding what the long running queries are.
>> You can then use explain analyse to see why they are long running.
>
> But is there a tool that could compile a summary out of the log? The log
> grows awefully big after a short time.
You might want to look at the "Practical Query Analyser" - haven't used
it myself yet, but it seems a sensible idea.
http://pqa.projects.postgresql.org/
--
Richard Huxton
Archonet Ltd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Raphael Bauduin | 2004-08-12 11:43:18 | Re: history tables with only one function? |
| Previous Message | Nikola Milutinovic | 2004-08-12 11:02:32 | PgSQL 8.0.0 beta1 compile problem + patch |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2004-08-12 13:39:46 | Re: Hardware upgrade for a high-traffic database |
| Previous Message | Ulrich Wisser | 2004-08-12 10:37:44 | Re: [GENERAL] How to know which queries are to be optimised? |