"Magnus Hagander" <[EMAIL PROTECTED]> writes:
> If I configure log_destination='eventlog', and then
> redirect_stderr='on', PostgreSQL will attempt to create a logfile in
> pg_log anyway.

So don't do that --- redirect_stderr is only sensible to turn on if you
mean to use logging to stderr.

The reason we don't attempt to enforce this is that log_destination is
legal to change after startup, whereas we can't change redirect_stderr
on-the-fly (because existing backends wouldn't have their stderr tied to
the right place).

I'm not sure how sensible it really is to switch dynamically between
logging to stderr and logging someplace else, but as long as the code
can support that, why not allow it ...

                        regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Reply via email to