Re: Full statement logging problematic on larger machines?

From: Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Frank Joerdens <frank(at)joerdens(dot)de>, pgsql-performance(at)postgresql(dot)org, Nic Ferrier <nic(at)woome(dot)com>, Avleen Vig <avleen(at)woome(dot)com>, Mike Rogers <mike(dot)rogers(at)woome(dot)com>
Subject: Re: Full statement logging problematic on larger machines?
Date: 2009-03-12 07:55:33
Message-ID: 1d4e0c10903120055p614e7d65g8a55d41faa94d346@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Thu, Mar 12, 2009 at 2:05 AM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> It is buffered at the individual log message level, so that we make sure we
> don't multiplex messages. No more than that.

OK. So if the OP can afford multiplexed queries by using a log
analyzer supporting them, it might be a good idea to try syslog with
full buffering.

--
Guillaume

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Nagalingam, Karthikeyan 2009-03-12 10:52:37 Entry point for Postgresql Performance
Previous Message Jignesh K. Shah 2009-03-12 03:48:44 Re: Proposal of tunable fix for scalability of 8.4