Received: from maia.hub.org (maia-2.hub.org [200.46.204.251])
	by mail.postgresql.org (Postfix) with ESMTP id 3D0E0633737
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Thu,  2 Sep 2010 16:03:42 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia,
	port 10024) with ESMTP id 39715-02 for
	<pgsql-admin-postgresql.org@mail.postgresql.org>;
	Thu,  2 Sep 2010 19:03:34 +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 147ED6335D8
	for <pgsql-admin@postgresql.org>; Thu,  2 Sep 2010 16:03:34 -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 o82J3XrU006301;
	Thu, 2 Sep 2010 15:03:33 -0400 (EDT)
To: A J <s5aly@yahoo.com>
cc: Kevin Grittner <Kevin.Grittner@wicourts.gov>,
	Scott Marlowe <scott.marlowe@gmail.com>, pgsql-admin@postgresql.org
Subject: Re: Confused by 'timing' results 
In-reply-to: <825153.47733.qm@web120009.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>
	<AANLkTi=6k6AbmBcqkVCKgNSiogVfQmP+iOC8FgA6+e5J@mail.gmail.com>
	<529329.89885.qm@web120007.mail.ne1.yahoo.com>
	<4C7F8F2A0200002500035037@gw.wicourts.gov>
	<294404.58402.qm@web120007.mail.ne1.yahoo.com>
	<27124.1283450803@sss.pgh.pa.us>
	<825153.47733.qm@web120009.mail.ne1.yahoo.com>
Comments: In-reply-to A J <s5aly@yahoo.com>
	message dated "Thu, 02 Sep 2010 11:10:45 -0700"
Date: Thu, 02 Sep 2010 15:03:33 -0400
Message-ID: <6300.1283454213@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
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/25
X-Sequence-Number: 35569

A J <s5aly@yahoo.com> writes:
> The performance as seen from the clients dropped substantially after turning on 
> the extra logging. The numbers were real but the performance dropped 
> significantly.

> All the log related settings in postgresql.conf are below:

Hmm, what about logging_collector?  (Or it might be called
redirect_stderr, depending on which PG version this is.)
If it's currently off, see whether turning it on improves matters.

			regards, tom lane