From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
Cc: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-committers(at)postgresql(dot)org |
Subject: | Re: pgsql-server/src backend/main/main.c backend/p ... |
Date: | 2004-05-19 13:02:40 |
Message-ID: | 15827.1084971760@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
"Magnus Hagander" <mha(at)sollentuna(dot)net> writes:
>>> I thought that output to stderr generally goes into the bit
>>> bucket in Windows.
> It is never ignored. WHen running as a service, you will only see it if
> ou check the box "allow service to interact with desktop", and this can
> only be done on Local System services (thus not postgresql) So in this
> case, the end effect will be that you can't see it. But you will most
> definitly see it when running it from the commandline (say, when you are
> debugging why it won't start..)
I guess the important question is whether it is possible to redirect
stderr into a file on Windows. If not, I'd say the output-to-stderr
option is pretty useless on that platform. I certainly don't want
critical messages sent to stderr with no possibility of capture.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2004-05-19 15:16:53 | Re: pgsql-server/src backend/main/main.c backend/p ... |
Previous Message | Magnus Hagander | 2004-05-19 08:06:09 | Re: pgsql-server/src backend/main/main.c backend/p ... |