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: | BANLkTinedFHCU48tn2--s1bi+dvdpfyWHQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
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.
> */
> #ifndef PG_SYSLOG_LIMIT
> #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
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Matthijs Bomhoff | 2011-06-29 19:20:49 | Re: Bug with plpgsql, temp tables and TOAST? |
Previous Message | Robert Haas | 2011-06-29 17:45:49 | Re: BUG #6063: compatability issues |