Re: Full statement logging problematic on larger machines?

From: Frank Joerdens <frank(at)joerdens(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com>, 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>, Andrew Dunstan <andrew(at)dunslane(dot)net>
Subject: Re: Full statement logging problematic on larger machines?
Date: 2009-03-12 13:38:56
Message-ID: 7d10d2df0903120638s3908aadbm5f285220fc738843@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Thu, Mar 12, 2009 at 1:45 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
[...]
> You could try changing _IOLBF
> to _IOFBF near the head of postmaster/syslogger.c and see if that helps.

I just put the patched .deb on staging and we'll give it a whirl there
for basic sanity checking - we currently have no way to even
approximate the load that we have on live for testing.

If all goes well I expect we'll put it on live early next week. I'll
let you know how it goes.

Regards,

Frank

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Dimitri Fontaine 2009-03-12 13:45:32 Re: Full statement logging problematic on larger machines?
Previous Message Ashish Karalkar 2009-03-12 11:10:14 Re: Entry point for Postgresql Performance