From: Tom Lane <tgl@sss.pgh.pa.us>
To: Evan Rempel <erempel@uvic.ca>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Syslog line wrapping
Date: Fri, 24 Sep 2010 00:21:32 -0400
Message-ID: <5956.1285302092@sss.pgh.pa.us> (raw)
In-Reply-To: <D768A8AD30B6E142BE50063CD6CCF5EE5DF632E337@EMC4.uvic.ca>
References: <D768A8AD30B6E142BE50063CD6CCF5EE5DF632E337@EMC4.uvic.ca>
Evan Rempel <erempel@uvic.ca> writes:
> I am running Postgresql 8.3 and would like to get postgres to
> NOT wrap the syslog lines. Is ther any configuration to do this.
> Perhaps I can wrap them at a very large line number?
The problem we're up against is explained in src/backend/utils/error/elog.c:
* Our problem here is that many syslog implementations don't handle long
* messages in an acceptable manner. While this function doesn't help that
* fact, it does work around by splitting up messages into smaller pieces.
If you are fortunate enough to have a less-broken-than-average syslog
facility, you could increase the PG_SYSLOG_LIMIT constant defined there.
On the whole, though, I'd suggest not depending on syslog. It has
other issues besides this one, like sometimes losing messages entirely.
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-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, erempel@uvic.ca
Subject: Re: Syslog line wrapping
In-Reply-To: <5956.1285302092@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