X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 663AD9DC8DB for ; Tue, 21 Mar 2006 05:56:42 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 17165-03 for ; Tue, 21 Mar 2006 05:56:43 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from maya.ngi.it (ns2.ngi.it [88.149.128.3]) by postgresql.org (Postfix) with ESMTP id 5FF699DC82D for ; Tue, 21 Mar 2006 05:56:35 -0400 (AST) Received: from [192.168.0.11] (194-185-53-252.f5.ngi.it [194.185.53.252]) by maya.ngi.it (8.13.5/8.13.5) with ESMTP id k2L9uZqd025539 for ; Tue, 21 Mar 2006 10:56:36 +0100 Message-ID: <441FCDD2.8010905@bluestudio.it> Date: Tue, 21 Mar 2006 10:56:34 +0100 From: Marco Furetto User-Agent: Mozilla Thunderbird 1.0.6-1.1.fc4 (X11/20050720) X-Accept-Language: en-us, en MIME-Version: 1.0 To: pgsql-performance@postgresql.org Subject: Re: Query Feromance References: <441EC34D.1000901@bluestudio.it> <001301c64c3c$3404b3f0$8b00000a@reimer> <441FB88E.2060801@bluestudio.it> <200603210943.57454.mlists@rp-online.de> In-Reply-To: <200603210943.57454.mlists@rp-online.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=1.726 required=5 tests=[AWL=-0.085, RCVD_IN_WHOIS_BOGONS=1.811] X-Spam-Score: 1.726 X-Spam-Level: * X-Archive-Number: 200603/367 X-Sequence-Number: 17804 ok, I enable query duration logging in postgresql.conf. where is the instruments for analyze the statistics queries executing on my db? Eg.: Number of query executing, total time for executing a single query, etc... Thank's Marco "Furetto" Berri Thomas Pundt wrote: > Hi, > > On Tuesday 21 March 2006 09:25, Marco Furetto wrote: > | I'm managing the db of a "Content Management environment" and I'm > | searching for a "Query analyzer" to improve performance because i don't > | know how many and what type of queries are executing on the system (for > | the "where and join" block). > > as a first step, I'd enable query duration logging; in postgresql.conf > I have set > > log_min_duration_statement = 3000 > > this will log each query that needs more than 3 seconds to complete. > > The next step would be to "explain analyze" the problematic queries. > > Ciao, > Thomas >