Re: BUG #5741: syslog line length

From: Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com>
To: pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: BUG #5741: syslog line length
Date: 2012-01-04 20:45:23
Message-ID: CALt0+o8Z0tvd7N=Z5eQbvWUYkX4kBbxyLNYBfBC7vVwcxVFbEw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

On Sat, Aug 6, 2011 at 12:18 AM, Noah Misch <noah(at)2ndquadrant(dot)com> wrote:
> A PG_SYSLOG_LIMIT value that loses data to truncation on nearly every default
> GNU/Linux installation makes for a poor default.

On Sat, Aug 6, 2011 at 3:03 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> OK, applied to HEAD and 9.1.

We hit this problem a few days ago on a server with RHEL 5 +
PostgreSQL 8.4 + syslog. It made it quite difficult to work on the
slow queries paralyzing the server as several of them had truncated
lines in the middle of them.

Any chance to have this fix backported to 8.4 and 9.0 as this is a
regression introduced in 8.4?

Thanks for your feedback.

--
Guillaume

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2012-01-04 21:21:37 Re: BUG #6379: SQL Function Causes Back-end Crash
Previous Message Paul Ramsey 2012-01-04 20:35:33 Re: BUG #6379: SQL Function Causes Back-end Crash