Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> [EMAIL PROTECTED] (Bruce Momjian) writes:
>>> Remove elog() calls from find_my_exec; do fprintf(stderr) instead.
>>
>> Isn't that a seriously bad idea?
> Yes, it probably is bad, but I am not sure how frequently this will
> happen, _
> >>> 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
"Magnus Hagander" <[EMAIL PROTECTED]> 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 o
> > > Remove elog() calls from find_my_exec; do
> fprintf(stderr) instead.
> >
> > Isn't that a seriously bad idea?
> >
> > I thought that output to stderr generally goes into the bit
> bucket in
> > Windows.
>
> I have never heard stderr is ignored in Win32. There was an
> issue that bu
> > > Yes, it probably is bad, but I am not sure how frequently
> this will
> > > happen, _and_ I need to set my_exec_path very far up in
> the tree to
> > > the timezone stuff knows the location, hence the fact that elog()
> > > calls wouldn't work at all anyway, I think.
> >
> > Perhaps the
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Yes, it probably is bad, but I am not sure how frequently this will
> > happen, _and_ I need to set my_exec_path very far up in the tree to the
> > timezone stuff knows the location, hence the fact that elog() calls
> > wouldn't work a
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Yes, it probably is bad, but I am not sure how frequently this will
> happen, _and_ I need to set my_exec_path very far up in the tree to the
> timezone stuff knows the location, hence the fact that elog() calls
> wouldn't work at all anyway, I think.
Pe
Tom Lane wrote:
> [EMAIL PROTECTED] (Bruce Momjian) writes:
> > Remove elog() calls from find_my_exec; do fprintf(stderr) instead.
>
> Isn't that a seriously bad idea?
>
> I thought that output to stderr generally goes into the bit bucket in
> Windows.
I have never heard stderr is ignored i
Tom Lane wrote:
> [EMAIL PROTECTED] (Bruce Momjian) writes:
> > Remove elog() calls from find_my_exec; do fprintf(stderr) instead.
>
> Isn't that a seriously bad idea?
>
> I thought that output to stderr generally goes into the bit bucket in
> Windows.
Yes, it probably is bad, but I am not
[EMAIL PROTECTED] (Bruce Momjian) writes:
> Remove elog() calls from find_my_exec; do fprintf(stderr) instead.
Isn't that a seriously bad idea?
I thought that output to stderr generally goes into the bit bucket in
Windows.
regards, tom lane
---
CVSROOT:/cvsroot
Module name:pgsql-server
Changes by: [EMAIL PROTECTED] 04/05/18 17:18:59
Modified files:
src/backend/main: main.c
src/backend/postmaster: postmaster.c
src/backend/tcop: postgres.c
src/bin/initdb : Makefile
src/bin/p
CVSROOT:/cvsroot
Module name:pgsql-server
Changes by: [EMAIL PROTECTED] 04/03/04 21:11:04
Modified files:
src/backend/main: main.c
src/backend/port/dynloader: win32.h
src/backend/postmaster: postmaster.c
src/bin/pg_resetxlog: Makefile
Log
12 matches
Mail list logo
