From: Frank Joerdens <frank@joerdens.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Guillaume Smet <guillaume.smet@gmail.com>
Cc: pgsql-performance@postgresql.org, Nic Ferrier <nic@woome.com>
Cc: Avleen Vig <avleen@woome.com>
Cc: Mike Rogers <mike.rogers@woome.com>
Cc: Andrew Dunstan <andrew@dunslane.net>
Subject: Re: Full statement logging problematic on larger machines?
Date: Thu, 12 Mar 2009 13:38:56 +0000
Message-ID: <7d10d2df0903120638s3908aadbm5f285220fc738843@mail.gmail.com> (raw)
In-Reply-To: <29255.1236822351@sss.pgh.pa.us>
References: <7d10d2df0903111227g2e40e742g5992cba5158dd4d2@mail.gmail.com>
<1d4e0c10903111659x6c96e6cau33ee121ee29a48a@mail.gmail.com>
<29255.1236822351@sss.pgh.pa.us>
On Thu, Mar 12, 2009 at 1:45 AM, Tom Lane <tgl@sss.pgh.pa.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: frank@joerdens.de, tgl@sss.pgh.pa.us, guillaume.smet@gmail.com, nic@woome.com, avleen@woome.com, mike.rogers@woome.com, andrew@dunslane.net
Subject: Re: Full statement logging problematic on larger machines?
In-Reply-To: <7d10d2df0903120638s3908aadbm5f285220fc738843@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox