Re: syslog_line_prefix - Mailing list pgsql-hackers

From Joshua Tolley
Subject Re: syslog_line_prefix
Date
Msg-id 20090925205807.GA2911@eddie
Whole thread Raw
In response to Re: syslog_line_prefix  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: syslog_line_prefix
Re: syslog_line_prefix
List pgsql-hackers
On Fri, Sep 25, 2009 at 03:19:36PM -0400, Tom Lane wrote:
> However, I don't think I actually believe the premise of this patch,
> which is that sending log information to both stderr and syslog is
> a useful thing to do

Actually the thing I want is to be able to send some stuff to syslog, and some
to a file, and other stuff to another file. This patch doesn't do all that,
but lays the necessary groundwork.

For instance, the various applications that parse query output all require
specific log line formats and various other configurations to be able to
understand our logs, and even then still have problems dealing with multi-line
entries. This is a pain. Such applications should be able to have their own
machine-readable logs, like csvlog. Unfortunately csvlogs are almost entirely
unreadable by humans, so I'd also like to have a human readable log somewhere.
These two logs need not necessarily contain the same information.

Loads of people seem to want to be able to have separate per-database log
files, which something like this could also allow.

--
Joshua Tolley / eggyknap
End Point Corporation
http://www.endpoint.com

pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: syslog_line_prefix
Next
From: Tom Lane
Date:
Subject: Re: 8.5 TODO: Add comments to output indicating version of pg_dump and of the database server