Skip site navigation (1) Skip section navigation (2)

Re: BUG #5741: syslog line length

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: heasley <heas(at)shrubbery(dot)net>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5741: syslog line length
Date: 2011-06-29 17:49:05
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
On Tue, Nov 2, 2010 at 12:17 PM, heasley <heas(at)shrubbery(dot)net> wrote:
> The following bug has been logged online:
> Bug reference:      5741
> Logged by:          heasley
> Email address:      heas(at)shrubbery(dot)net
> PostgreSQL version: 8.4
> Operating system:   solaris
> Description:        syslog line length
> Details:
> * Max string length to send to syslog().  Note that this doesn't count the
>  * sequence-number prefix we add, and of course it doesn't count the prefix
>  * added by syslog itself.      On many implementations it seems that the
> hard
>  * limit is approximately 2K bytes including both those prefixes.
>  */
> #define PG_SYSLOG_LIMIT 1024
> #endif
> solaris' syslogd limits the line length to 1024, with a
> FQDN and it's silly "msg ID" quite a bit is dropped by
> syslogd.

You can recompile with -DPG_SYSLOG_LIMIT=<some smaller value>.

We could add a configuration setting for this, if it's affecting a lot
of people.

Robert Haas
The Enterprise PostgreSQL Company

In response to


pgsql-bugs by date

Next:From: Matthijs BomhoffDate: 2011-06-29 19:20:49
Subject: Re: Bug with plpgsql, temp tables and TOAST?
Previous:From: Robert HaasDate: 2011-06-29 17:45:49
Subject: Re: BUG #6063: compatability issues

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group