From: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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 15:16:53 |
Message-ID: | 6BCB9D8A16AC4241919521715F4D8BCE34BA63@algol.sollentuna.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
> >>> 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.
It is. From the commandline, not from a service. (You could do it from a
service wrapper, I think, but somebody reported problems with that
earlier)
//Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-05-19 16:31:07 | Re: pgsql-server/src backend/main/main.c backend/p ... |
Previous Message | Tom Lane | 2004-05-19 13:02:40 | Re: pgsql-server/src backend/main/main.c backend/p ... |