From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
---|---|
To: | Ulrich Wisser <ulrich(dot)wisser(at)relevanttraffic(dot)se> |
Cc: | pgsql-general(at)postgresql(dot)org, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: How to know which queries are to be optimised? |
Date: | 2004-08-11 16:27:01 |
Message-ID: | 20040811162701.GA9992@wolff.to |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-performance |
On Wed, Aug 04, 2004 at 14:00:39 +0200,
Ulrich Wisser <ulrich(dot)wisser(at)relevanttraffic(dot)se> wrote:
This topic really belongs on the performance list. I have copied that
list and set followups to go there and copy you.
>
> my web application grows slower and slower over time. After some
> profiling I came to the conclusion that my SQL queries are the biggest
> time spenders (25 seconds). Obviously I need to optimise my queries and
> maybe introduce some new indexes.
This sounds like you aren't doing proper maintainance. You need to be
vacuuming with a large enough FSM setting.
> The problem is, that my application uses dynamic queries. I therefor can
> not determine what are the most common queries.
>
> I have used the postgresql logging ption before. Is there a tool to
> analyze the logfile for the most common and/or most time consuming queries?
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-08-11 16:28:51 | Re: psql: immediately exit after an error? |
Previous Message | Tom Lane | 2004-08-11 16:02:07 | Re: Replication options? |
From | Date | Subject | |
---|---|---|---|
Next Message | Jesper Krogh | 2004-08-11 16:29:33 | Re: Storing binary data. |
Previous Message | Tom Lane | 2004-08-11 16:06:38 | Re: Storing binary data. |