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 74D779DCBFE for ; Tue, 21 Mar 2006 04:40:48 -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 04123-04 for ; Tue, 21 Mar 2006 04:40:48 -0400 (AST) Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 22EA79DCB9F for ; Tue, 21 Mar 2006 04:40:46 -0400 (AST) Received: from mail.rp-online.de (mail.rp-online.de [149.221.1.199]) by svr4.postgresql.org (Postfix) with ESMTP id 11B5F5AF663 for ; Tue, 21 Mar 2006 08:40:47 +0000 (GMT) Received: from idefix.d.rp-online.de (idefix.d.rp-online.de [149.221.100.194]) by mail.rp-online.de (Postfix) with ESMTP id 1AA081CF8E for ; Tue, 21 Mar 2006 09:40:44 +0100 (CET) From: Thomas Pundt Reply-To: Thomas Pundt Organization: RP Online Verlagsgesellschaft mbH To: pgsql-performance@postgresql.org Subject: Re: Query Feromance Date: Tue, 21 Mar 2006 09:43:57 +0100 User-Agent: KMail/1.9.1 References: <441EC34D.1000901@bluestudio.it> <001301c64c3c$3404b3f0$8b00000a@reimer> <441FB88E.2060801@bluestudio.it> In-Reply-To: <441FB88E.2060801@bluestudio.it> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603210943.57454.mlists@rp-online.de> X-Anti-Virus: Kaspersky Anti-Virus for MailServers 5.5.3/RELEASE, bases: 21032006 #172112, status: clean X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0 required=5 tests=[none] X-Spam-Score: 0 X-Spam-Level: X-Archive-Number: 200603/365 X-Sequence-Number: 17802 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 -- Thomas Pundt ---- http://rp-online.de/ ----