| From: | Noah Misch <noah(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-bugs(at)postgresql(dot)org, Marc Cousin <cousinmarc(at)gmail(dot)com> |
| Subject: | Re: BUG #5741: syslog line length |
| Date: | 2011-08-05 23:18:17 |
| Message-ID: | 20110805231816.GD419@tornado.leadboat.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Aug 05, 2011 at 06:46:21PM -0400, Tom Lane wrote:
> Noah Misch <noah(at)2ndQuadrant(dot)com> writes:
> > A PG_SYSLOG_LIMIT value that loses data to truncation on nearly every default
> > GNU/Linux installation makes for a poor default.
>
> When I changed it, it was on the strength of tests showing that Fedora
> 8's default syslogger had a limit of 2KB. A quick check shows this is
> still the case in Fedora 15. So I'm not convinced that "nearly every"
> is anywhere near true.
Point taken. Marc hit the 1024 limit in RHEL 5, which appears to be based on
Fedora 6. Perhaps Fedora began to patch in the higher limit in 7 or 8. I also
observed the 1024 limit in Ubuntu 8.04 LTS. It is the limit in the latest
source distributions of sysklogd, too.
> > How about 896?
>
> But having said that, I could go with 896 (or perhaps 900, which seems
> a shade less weird).
That works for me.
--
Noah Misch http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| syslog-limit-900.patch | text/plain | 1008 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-08-06 01:03:51 | Re: BUG #5741: syslog line length |
| Previous Message | Christoph Anton Mitterer | 2011-08-05 23:02:49 | BUG #6153: possible typo in the local_preload_libraries documentation |