From: Guillaume Smet <guillaume.smet@gmail.com>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Frank Joerdens <frank@joerdens.de>
Cc: pgsql-performance@postgresql.org, Nic Ferrier <nic@woome.com>
Cc: Avleen Vig <avleen@woome.com>
Cc: Mike Rogers <mike.rogers@woome.com>
Subject: Re: Full statement logging problematic on larger machines?
Date: Thu, 12 Mar 2009 08:55:33 +0100
Message-ID: <1d4e0c10903120055p614e7d65g8a55d41faa94d346@mail.gmail.com> (raw)
In-Reply-To: <49B85FD9.7050406@dunslane.net>
References: <7d10d2df0903111227g2e40e742g5992cba5158dd4d2@mail.gmail.com>
<1d4e0c10903111659x6c96e6cau33ee121ee29a48a@mail.gmail.com>
<49B85FD9.7050406@dunslane.net>
On Thu, Mar 12, 2009 at 2:05 AM, Andrew Dunstan <andrew@dunslane.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
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: guillaume.smet@gmail.com, andrew@dunslane.net, frank@joerdens.de, nic@woome.com, avleen@woome.com, mike.rogers@woome.com
Subject: Re: Full statement logging problematic on larger machines?
In-Reply-To: <1d4e0c10903120055p614e7d65g8a55d41faa94d346@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