X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 31CEC8B9ED9 for ; Tue, 8 Feb 2005 01:41:02 +0000 (GMT) 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 29848-05 for ; Tue, 8 Feb 2005 01:40:48 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.183]) by svr1.postgresql.org (Postfix) with ESMTP id 567358B9EA3 for ; Tue, 8 Feb 2005 01:40:50 +0000 (GMT) Received: from [212.227.126.208] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1CyKMz-0003T3-00; Tue, 08 Feb 2005 02:40:49 +0100 Received: from [192.59.128.130] (helo=stromboli) by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1) id 1CyKMy-0003o8-00; Tue, 08 Feb 2005 02:40:48 +0100 From: "Simon Riggs" To: "Tom Lane" Cc: Subject: Re: log_duration Date: Mon, 7 Feb 2005 16:40:39 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <4984.1107711157@sss.pgh.pa.us> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Importance: Normal X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:51320d06ba6b43864a3fe5d428030dbe X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.014 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200502/56 X-Sequence-Number: 16224 >Tom Lane > "Simon Riggs" writes: > > Further update on this: > > > We've isolated this issue to JDBC client access. > > Ah-hah, now it makes sense. I believe the JDBC driver always uses > extended query protocol (parse/bind/execute messages). Thanks for the *solution. I had a D'Oh moment about 2 hours after I posted... > As a quick workaround until someone thinks of a better idea, > it might be > sufficient to attach logging code to the execute phase, and ignore the > partial-execution issue. Done... we're getting results out now. I'm logging both duration of execution and the statement text, as would be displayed in pg_stat_activity. Thanks, Best Regards, Simon Riggs