X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 4F51FD7206 for ; Tue, 11 Oct 2005 11:04:34 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 41774-07 for ; Tue, 11 Oct 2005 14:04:27 +0000 (GMT) Received: from mallaury.nerim.net (smtp-102-tuesday.noc.nerim.net [62.4.17.102]) by svr1.postgresql.org (Postfix) with ESMTP id 057AFD71E9 for ; Tue, 11 Oct 2005 11:04:30 -0300 (ADT) Received: from jobmare.clarisys.lan (claridsl512.net1.nerim.net [213.41.148.137]) by mallaury.nerim.net (Postfix) with ESMTP id CA2F54F41D; Tue, 11 Oct 2005 16:04:24 +0200 (CEST) Received: from day by jobmare.clarisys.lan with local (Exim 4.52) id 1EPKkg-0007Lt-H2; Tue, 11 Oct 2005 16:05:10 +0200 Date: Tue, 11 Oct 2005 16:05:10 +0200 From: David Pradier To: "Jim C. Nasby" Cc: pgsql-admin@postgresql.org Subject: Re: A tool to extract the problematic points of the postgresl log. Message-ID: <20051011140510.GF12162@clarisys.fr> References: <20051011095929.GD12162@clarisys.fr> <20051011134626.GR23883@pervasive.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051011134626.GR23883@pervasive.com> User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.05 required=5 tests=[FORGED_RCVD_HELO=0.05] X-Spam-Level: X-Archive-Number: 200510/125 X-Sequence-Number: 19197 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