Re: Confused by 'timing' results

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(at)sss(dot)pgh(dot)pa(dot)us>
To: A J <s5aly(at)yahoo(dot)com>
Cc: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>; Scott Marlowe
<scott(dot)marlowe(at)gmail(dot)com>; pgsql-admin(at)postgresql(dot)org
Sent: Thu, September 2, 2010 3:03:33 PM
Subject: Re: [ADMIN] Confused by 'timing' results

A J <s5aly(at)yahoo(dot)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