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 8F15FD6F01 for ; Tue, 11 Oct 2005 11:36:11 -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 34919-07 for ; Tue, 11 Oct 2005 14:36:06 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 3F136D6E41 for ; Tue, 11 Oct 2005 11:36:09 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.13.1/8.13.1) with ESMTP id j9BEa5MU060456 for ; Tue, 11 Oct 2005 14:36:05 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.13.1/8.13.1/Submit) id j9BEDgKZ096638 for pgsql-admin@postgresql.org; Tue, 11 Oct 2005 14:13:42 GMT (envelope-from news) From: Hannes Dorbath X-Newsgroups: pgsql.admin Subject: Re: A tool to extract the problematic points of the postgresl log. Date: Tue, 11 Oct 2005 16:14:05 +0200 Organization: Hub.Org Networking Services Lines: 24 Message-ID: References: <20051011095929.GD12162@clarisys.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@news.hub.org User-Agent: Thunderbird 1.4 (Windows/20050908) In-Reply-To: <20051011095929.GD12162@clarisys.fr> To: pgsql-admin@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=-2.417 required=5 tests=[ALL_TRUSTED=-2.82, AWL=0.403] X-Spam-Level: X-Archive-Number: 200510/126 X-Sequence-Number: 19198 http://pqa.projects.postgresql.org/ You need to have ruby installed, though. On 11.10.2005 11:59, 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 ? -- Regards, Hannes Dorbath