Digging into several win32 related issues right now, so I don't have the
time to investigate ATM, but I figured I should get it out here:
If I configure log_destination='eventlog', and then
redirect_stderr='on', PostgreSQL will attempt to create a logfile in
pg_log anyway. This file remains empty
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
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.
I don't. Normally. But I had it turned on,
