From: David Pradier <david.pradier@clarisys.fr>
To: Jim C. Nasby <jnasby@pervasive.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: A tool to extract the problematic points of the postgresl log.
Date: Tue, 11 Oct 2005 16:05:10 +0200
Message-ID: <20051011140510.GF12162@clarisys.fr> (raw)
In-Reply-To: <20051011134626.GR23883@pervasive.com>
References: <20051011095929.GD12162@clarisys.fr>
<20051011134626.GR23883@pervasive.com>
I think i've found the right tool on pgfoundry.org :
http://pqa.projects.postgresql.org/example.html
Thanks for your advice.
Best regards,
David
On Tue, Oct 11, 2005 at 08:46:26AM -0500, Jim C. Nasby wrote:
> Yes, someone has. Take a look on http://pgfoundry.org; I'm pretty sure
> it's there.
>
> On Tue, Oct 11, 2005 at 11:59:29AM +0200, David Pradier wrote:
> > 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
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 9: In versions below 8.0, the planner will ignore your desire to
> > choose an index scan if your joining column's datatypes do not
> > match
> >
>
> --
> Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com
> Pervasive Software http://pervasive.com work: 512-231-6117
> vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
--
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, jnasby@pervasive.com
Subject: Re: A tool to extract the problematic points of the postgresl log.
In-Reply-To: <20051011140510.GF12162@clarisys.fr>
References: <20051011095929.GD12162@clarisys.fr> <20051011134626.GR23883@pervasive.com> <20051011140510.GF12162@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