From: Tom Lane <tgl@sss.pgh.pa.us>
To: Achilleas Mantzios <achill@matrix.gatewaynet.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: syslog performance when logging big statements
Date: Tue, 08 Jul 2008 10:35:16 -0400
Message-ID: <8675.1215527716@sss.pgh.pa.us> (raw)
In-Reply-To: <200807081524.47366.achill@matrix.gatewaynet.com>
References: <200807081524.47366.achill@matrix.gatewaynet.com>
Achilleas Mantzios <achill@matrix.gatewaynet.com> writes:
> In this case, the INSERT *needs* 20 minutes to return. This is because the logging through syslog seems to severely slow the system.
> If instead, i use stderr, even with logging_collector=on, the same statement needs 15 seconds to return.
Hmm. There's a function in elog.c that breaks log messages into chunks
for syslog. I don't think anyone's ever looked hard at its performance
--- maybe there's an O(N^2) behavior?
regards, tom lane
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: tgl@sss.pgh.pa.us, achill@matrix.gatewaynet.com
Subject: Re: syslog performance when logging big statements
In-Reply-To: <8675.1215527716@sss.pgh.pa.us>
* 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