Skip site navigation (1) Skip section navigation (2)

Re: pgsql-server/src backend/main/main.c backend/p ...

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: (view raw, whole thread or download thread mbox)
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

In response to

pgsql-committers by date

Next:From: Magnus HaganderDate: 2004-05-19 15:16:53
Subject: Re: pgsql-server/src backend/main/main.c backend/p ...
Previous:From: Magnus HaganderDate: 2004-05-19 08:06:09
Subject: Re: pgsql-server/src backend/main/main.c backend/p ...

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group