Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id E68936349D4 for ; Thu, 2 Sep 2010 16:08:08 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 43413-08 for ; Thu, 2 Sep 2010 19:08:01 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from n1-vm0.bullet.mail.gq1.yahoo.com (n1-vm0.bullet.mail.gq1.yahoo.com [67.195.23.152]) by mail.postgresql.org (Postfix) with SMTP id 09EBA6335D8 for ; Thu, 2 Sep 2010 16:07:57 -0300 (ADT) Received: from [67.195.9.83] by n1.bullet.mail.gq1.yahoo.com with NNFMP; 02 Sep 2010 19:07:56 -0000 Received: from [98.137.27.216] by t3.bullet.mail.gq1.yahoo.com with NNFMP; 02 Sep 2010 19:07:56 -0000 Received: from [127.0.0.1] by omp126.mail.gq1.yahoo.com with NNFMP; 02 Sep 2010 19:07:56 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 317756.28541.bm@omp126.mail.gq1.yahoo.com Received: (qmail 38462 invoked by uid 60001); 2 Sep 2010 19:07:56 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1283454475; bh=2FJoIuoavQRtx5R6op1NsQk9y+D5ySL7EzszPLZe6ZI=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=qYUb12YBYkhWgv57khnBTcLmtOSOEH22u/5Wph3IPCTd9UWLumAYlJM7BeIB5coD5vDykxVfsqoQ64v2a/7dp8jzuog7JiBkwHCEt2xxDZpqbctzCV/QNu+FaG47zV46YN99lyb7kmvnc2ky4Y2S4g1ZRTwM5V8Y3OrfP9vUUEI= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=LuE7q4NeKyfv1iySxHOBc5VoS4ACALj4aVp8uvIpc8igmsBZuPjhil9G3YQk3U2g1GUhUY40a5e3iVMhJcq04Hd16V4NRNe8Y/KCt6SDeIN4s+tKdW7HySgxQ51XhlsGW0rjbrJeUF0KTc0m3x58f+eil70ehXybfEhgsnvNjNM=; Message-ID: <919275.37963.qm@web120002.mail.ne1.yahoo.com> X-YMail-OSG: BqowAdoVM1mMBuxZDpXZzYIcHLMJpSVM4BQMsxRhCxbLL63 aiJqrh6jAFBTi7wpRi1Tq1UbAtpUnYOdKxuSb7YxOdFKBwNeJV7ZdOOsgXCm kdoYKe69QqkWaGZYMd_USOiMVmG7yQ9OJc5GNiu4yyL73oGHkNc875KpNV6M j3LbqIPOTvOYYjGx2jPSfdXl2KLcGEoF7DaRo0z5rGnGp6c0XozOkTaKnO_s 6OsShjl_YxNQIejrpgA-- Received: from [68.36.215.11] by web120002.mail.ne1.yahoo.com via HTTP; Thu, 02 Sep 2010 12:07:55 PDT X-Mailer: YahooMailRC/470 YahooMailWebService/0.8.105.279950 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> <27124.1283450803@sss.pgh.pa.us> <825153.47733.qm@web120009.mail.ne1.yahoo.com> <6300.1283454213@sss.pgh.pa.us> Date: Thu, 2 Sep 2010 12:07:55 -0700 (PDT) From: A J Subject: Re: Confused by 'timing' results To: Tom Lane Cc: Kevin Grittner , Scott Marlowe , pgsql-admin@postgresql.org In-Reply-To: <6300.1283454213@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1337930460-1283454475=:37963" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.909 tagged_above=-10 required=5 tests=BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201009/26 X-Sequence-Number: 35570 --0-1337930460-1283454475=:37963 Content-Type: text/plain; charset=us-ascii Sorry, forgot to mention that: logging_collector = on # Enable capturing of stderr and csvlog Infact I was thinking of the other way, to switch it off and somehow display the stderr(or syslog) directly on console (rather than writing to a file) to see if it helps. ________________________________ From: Tom Lane To: A J Cc: Kevin Grittner ; Scott Marlowe ; pgsql-admin@postgresql.org Sent: Thu, September 2, 2010 3:03:33 PM Subject: Re: [ADMIN] Confused by 'timing' results A J 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 -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin --0-1337930460-1283454475=:37963 Content-Type: text/html; charset=us-ascii
Sorry, forgot to mention that:
logging_collector = on          # Enable capturing of stderr and csvlog

Infact I was thinking of the other way, to switch it off and somehow display the stderr(or syslog) directly on console (rather than writing to a file) to see if it helps.


From: Tom Lane <tgl@sss.pgh.pa.us>
To: A J <s5aly@yahoo.com>
Cc: Kevin Grittner <Kevin.Grittner@wicourts.gov>; Scott Marlowe <scott.marlowe@gmail.com>; pgsql-admin@postgresql.org
Sent: Thu, September 2, 2010 3:03:33 PM
Subject: Re: [ADMIN] Confused by 'timing' results

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

--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin

--0-1337930460-1283454475=:37963--