X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 0B59552802 for ; Tue, 12 Jul 2005 22:14:46 -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 57461-07 for ; Wed, 13 Jul 2005 01:14:37 +0000 (GMT) Received: from houston.familyhealth.com.au (houston.au.fhnetwork.com [203.22.197.21]) by svr1.postgresql.org (Postfix) with ESMTP id 0168752965 for ; Tue, 12 Jul 2005 22:14:33 -0300 (ADT) Received: from houston.familyhealth.com.au (localhost [127.0.0.1]) by houston.familyhealth.com.au (Postfix) with ESMTP id 97D5824FE1; Wed, 13 Jul 2005 09:14:33 +0800 (WST) Received: from [127.0.0.1] (work-40.internal [192.168.0.40]) by houston.familyhealth.com.au (Postfix) with ESMTP id 7E63124FE0; Wed, 13 Jul 2005 09:14:33 +0800 (WST) Message-ID: <42D46BC4.2010907@familyhealth.com.au> Date: Wed, 13 Jul 2005 09:17:56 +0800 From: Christopher Kings-Lynne User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dennis Cc: pgsql-performance@postgresql.org Subject: Re: General DB Tuning References: <20050712233230.5466.qmail@web33901.mail.mud.yahoo.com> <42D4621D.4060803@jobflash.com> <42D468C9.9070200@works4me.com> In-Reply-To: <42D468C9.9070200@works4me.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.063 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200507/130 X-Sequence-Number: 13371 >> we are using jdbc -- the "log_min_duration_statement = 3000 " >> statement works fine for me. Looks like there's no other work around >> for the bug(?). Not sure since I have no interest in logging a >> million statements a day, I only want to see the poorly performing hits. > > Doesn't it depend on what jdbc driver you are using? It depends if he's using new-protocol prepared queries which don't get logged properly. Wasn't that fixed for 8.1 or something? Chris