Re: Confused by 'timing' results - Mailing list pgsql-admin

From A J
Subject Re: Confused by 'timing' results
Date
Msg-id 919275.37963.qm@web120002.mail.ne1.yahoo.com
Whole thread Raw
In response to Re: Confused by 'timing' results  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-admin
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

pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: Confused by 'timing' results
Next
From: "Kevin Grittner"
Date:
Subject: Re: Confused by 'timing' results