Re: Updated logging config (was: Initial eventlog support on win32 ) - Mailing list pgsql-patches

From Magnus Hagander
Subject Re: Updated logging config (was: Initial eventlog support on win32 )
Date
Msg-id 6BCB9D8A16AC4241919521715F4D8BCE34B5BC@algol.sollentuna.se
Whole thread Raw
Responses Re: Updated logging config (was: Initial eventlog support on win32 )
Re: Updated logging config (was: Initial eventlog support on win32 )
List pgsql-patches
Something about like this?

(If approved ,documentation patches of course comeing up, but I'd like
to have the syntax and ide approved before I get into that)

This patch also includes the eventlog code for win32.

//Magnus


>-----Original Message-----
>From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
>Sent: den 23 mars 2004 16:02
>To: Magnus Hagander
>Cc: Andrew Dunstan; pgsql-patches@postgresql.org
>Subject: Re: [PATCHES] Initial eventlog support on win32
>
>
>"Magnus Hagander" <mha@sollentuna.net> writes:
>> Based on what Andrew wrote, configuration along the line of:
>> log_destination        stdout
>> (for default)
>
>> log_destination        stdout,syslog
>> (for syslog=2)
>
>> log_destination        eventlog
>> (for win32 eventlog only)
>
>> etc etc.
>
>Should be "stderr" not "stdout".  Otherwise looks good.  I
>think you can
>find existing infrastructure for parsing a comma-separated list of
>keywords in a GUC variable --- look at how DateStyle is handled.
>
>            regards, tom lane
>

Attachment

pgsql-patches by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Small comment fix in s_lock.c
Next
From: Tom Lane
Date:
Subject: Re: dollar quoting and pg_dump