Re: Updated logging config (was: Initial eventlog support on win32 )

From: "Magnus Hagander" <mha(at)sollentuna(dot)net>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Updated logging config (was: Initial eventlog support on win32 )
Date: 2004-07-23 22:03:55
Message-ID: 6BCB9D8A16AC4241919521715F4D8BCE34BF0B@algol.sollentuna.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

>However, there certainly wasn't any reason that the syslog-vs-stderr
>switch couldn't be flipped on the fly; the only reason it's even
>PGC_SIGHUP was we wanted to enforce that all backends are doing the
>same thing at any given time.

Right.

>I was just wondering if the log_destination change had introduced any
>new constraints I didn't know about (in particular, what about
>eventlog?)

Shouldn't.
The eventlog is automatically initialised the first time it's called in
each process (using the static variable evtHandle). So it shouldn't make
any difference when you change it.

//Magnus

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2004-07-23 22:04:29 Re: logfile subprocess and Fancy File Functions
Previous Message Bruce Momjian 2004-07-23 21:56:08 Re: logfile subprocess and Fancy File Functions