Re: syslog configurable line splitting behavior

From: Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: syslog configurable line splitting behavior
Date: 2016-03-04 16:01:26
Message-ID: CAPpHfdvpUR6dYrXFm0Dj9ThW4_=rAQ3QafJzqDLmBsd82rrz8w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Feb 27, 2016 at 6:49 AM, Peter Eisentraut <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?

------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2016-03-04 16:02:15 Re: postgres_fdw vs. force_parallel_mode on ppc
Previous Message Alvaro Herrera 2016-03-04 15:52:54 Re: silent data loss with ext4 / all current versions