From: David Pradier <david.pradier@clarisys.fr>
To: pgsql-admin@postgresql.org
Subject: A tool to extract the problematic points of the postgresl log.
Date: Tue, 11 Oct 2005 11:59:29 +0200
Message-ID: <20051011095929.GD12162@clarisys.fr> (raw)
Hi everybody,
i'd like to know if my database (settings, indexes, materialized views,
etc) is correctly tuned.
To do this, i think the best way is to watch the queries actually
processed and the time needed.
The postgres log is the right way to do this, i think.
But well, it's a bit dense.
Nothing i can't go through, but would you know a better tool than grep
to parse the file and extract the problematic points ?
As it might be a common problem, maybe somebody as already written a
generic tool to do this ?
Thanks in advance,
David
--
David Pradier -- Directeur Technique de Clarisys Informatique -- Chef de projet logiciels libres / open-source
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: david.pradier@clarisys.fr
Subject: Re: A tool to extract the problematic points of the postgresl log.
In-Reply-To: <20051011095929.GD12162@clarisys.fr>
References: <20051011095929.GD12162@clarisys.fr>
* 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