From: Richard Huxton <dev@archonet.com>
To: Ulrich Wisser <ulrich.wisser@relevanttraffic.se>
Cc: pgsql-performance@postgresql.org
Cc: bruno@wolff.to
Subject: Re: [GENERAL] How to know which queries are to be optimised?
Date: Thu, 12 Aug 2004 12:16:20 +0100
Message-ID: <411B5184.6090106@archonet.com> (raw)
In-Reply-To: <411B4878.4090804@relevanttraffic.se>
References: <4110CFE7.9000202@relevanttraffic.se>
<20040811162701.GA9992@wolff.to>
<411B4878.4090804@relevanttraffic.se>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: dev@archonet.com, ulrich.wisser@relevanttraffic.se, bruno@wolff.to
Subject: Re: [GENERAL] How to know which queries are to be optimised?
In-Reply-To: <411B5184.6090106@archonet.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox