Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 61990632898 for ; Thu, 2 Sep 2010 15:06:53 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 85016-06 for ; Thu, 2 Sep 2010 18:06:44 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id EF33463265B for ; Thu, 2 Sep 2010 15:06:44 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id o82I6h8c027125; Thu, 2 Sep 2010 14:06:44 -0400 (EDT) To: A J cc: Kevin Grittner , Scott Marlowe , pgsql-admin@postgresql.org Subject: Re: Confused by 'timing' results In-reply-to: <294404.58402.qm@web120007.mail.ne1.yahoo.com> References: <788866.21140.qm@web120020.mail.ne1.yahoo.com> <4C7D00330200002500034ED2@gw.wicourts.gov> <19320.56933.qm@web120013.mail.ne1.yahoo.com> <529329.89885.qm@web120007.mail.ne1.yahoo.com> <4C7F8F2A0200002500035037@gw.wicourts.gov> <294404.58402.qm@web120007.mail.ne1.yahoo.com> Comments: In-reply-to A J message dated "Thu, 02 Sep 2010 10:34:30 -0700" Date: Thu, 02 Sep 2010 14:06:43 -0400 Message-ID: <27124.1283450803@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201009/21 X-Sequence-Number: 35565 A J writes: > On second try, by trying to log to log_directory/log_filename by > setting log_min_duration_statement=0, seems to be doing something weird. The > durations are very very high in the file and cannot be true. You're not being very clear here. Did the logged durations not correspond to reality? Or did the performance as seen from the clients drop substantially when you turned on extra logging? Also, exactly how are you doing logging (ie, what are your settings for log_destination and related parameters)? regards, tom lane