Re: syslog_line_prefix - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: syslog_line_prefix
Date
Msg-id 9837222c0909251401g6638874dk3eebdabfc87ef88f@mail.gmail.com
Whole thread Raw
In response to Re: syslog_line_prefix  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: syslog_line_prefix
List pgsql-hackers
On Fri, Sep 25, 2009 at 22:57, Andrew Dunstan <andrew@dunslane.net> wrote:
>
> Magnus Hagander wrote:
>>
>> On Fri, Sep 25, 2009 at 22:17, Andrew Dunstan <andrew@dunslane.net> wrote:
>>
>>>
>>> Magnus Hagander wrote:
>>>
>>>>
>>>> I definitely want both text and CSV output - which I can't have today.
>>>>
>>>
>>> Sure you can. What makes you think you can't?
>>>
>>
>> How do i do that? When I enable csv logging, it changes the log format
>> to csv, and my plaintext logs don't end up in the logs anymore.
>>
>> Note that I'm not talking about syslog, I'm talking about the logging
>> that goes through the logging collector, and is dealt with by
>> PostgreSQL.
>>
>>
>
> log_destination = 'stderr, csvlog'

Clearly that works. I wonder why that didn't work when I last tried it :S

/me wipes the egg off.

(it's still weird that it's called stderr when it's a logfile, but
that's a different story)


Without looking deeply at the code, does it also properly route these
famous "messages from third party libraries" to both files?

-- Magnus HaganderMe: http://www.hagander.net/Work: http://www.redpill-linpro.com/


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: syslog_line_prefix
Next
From: Tom Lane
Date:
Subject: Re: WIP - syslogger infrastructure changes