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 5A9359DD572 for ; Wed, 22 Mar 2006 05:18:26 -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 93925-07 for ; Wed, 22 Mar 2006 05:18:26 -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 2C0F39DD560 for ; Wed, 22 Mar 2006 05:18:22 -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 k2M9IMdp017634 for ; Wed, 22 Mar 2006 10:18:23 +0100 Message-ID: <4421165E.4070800@bluestudio.it> Date: Wed, 22 Mar 2006 10:18:22 +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=0.683 required=5 tests=[AWL=0.683] X-Spam-Score: 0.683 X-Spam-Level: X-Archive-Number: 200603/441 X-Sequence-Number: 17878 I find another java program for monitory application query: http://www.p6spy.com/ with interface http://www.jahia.net/jahia/page597.html 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 >