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

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: win32 service code


  • 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: Thu, 27 May 2004 21:45:00 +0200
  • Message-id: <6BCB9D8A16AC4241919521715F4D8BCE34BB4F(at)algol(dot)sollentuna(dot)se>

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



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group