From: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
---|---|
To: | "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> |
Cc: | "PgSql-Win32" <pgsql-hackers-win32(at)postgresql(dot)org> |
Subject: | Re: win32 service code |
Date: | 2004-05-27 19:45:00 |
Message-ID: | 6BCB9D8A16AC4241919521715F4D8BCE34BB4F@algol.sollentuna.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers-win32 |
>> 3) Include in postmaster but running on a separate thread
>(not process
>> as (2))
>> Advantages: No extra binary. No extra process. Most integration.
>> Disadvantages: Probably larger impact on postmaster code.
>
>This is the best way to go, I think. This way we can automatically
>redirect stderr to the event logger and other nice stuff like that.
How can we do this in this case when we can't do it from another
process?
(Note - only "boot messages" are interesting anyway. Once the ereport
code is activated (and after GUC loads), we will report directly to the
eventlog.
>Also this prevents having to deal weird problem like the postmaster
>crashing but postserver.exe still running...yuck.
Yes, that is a definite advantage.
//Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2004-05-27 20:11:05 | Re: win32 service code |
Previous Message | Merlin Moncure | 2004-05-27 19:28:50 | Re: win32 service code |