>> 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
