From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: syslog configurable line splitting behavior |
Date: | 2016-03-09 02:19:40 |
Message-ID: | 56DF883C.1090600@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 3/4/16 11:01 AM, Alexander Korotkov wrote:
> On Sat, Feb 27, 2016 at 6:49 AM, Peter Eisentraut <peter_e(at)gmx(dot)net
> <mailto:peter_e(at)gmx(dot)net>> wrote:
>
> Writing log messages to syslog caters to ancient syslog implementations
> in two ways:
>
> - sequence numbers
> - line splitting
>
> While these are arguably reasonable defaults, I would like a way to turn
> them off, because they get in the way of doing more interesting things
> with syslog (e.g., logging somewhere that is not just a text file).
>
> So I propose the two attached patches that introduce new configuration
> Boolean parameters syslog_sequence_numbers and syslog_split_lines that
> can toggle these behaviors.
>
>
> Would it have any usage if we make PG_SYSLOG_LIMIT configurable (-1 for
> disable) instead of introducing boolean?
That would work, too. But then we'd need another setting to disable
splitting on newlines. That way we'd have more settings, but they
actually mirror the corresponding settings on the rsyslogd side better.
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2016-03-09 02:20:27 | Re: syslog configurable line splitting behavior |
Previous Message | Andreas Karlsson | 2016-03-09 02:12:31 | Re: syslog configurable line splitting behavior |