> 1) Separate binary "pgservice.exe" that will CreateProcess() the
> Advantages: Zero impact on postmaster code. Simple to do.
> Disadvantages: Adds a platform-specific binary.
My preference. Personally, I think we should make this pg_ctl.
> 2) Include in postmaster doing an extra CreateProcess().
> Advantages: No extra binary. Low impact on postmaster code.
> Disadvantages: Two postmaster.exe:s. running (confusing? overhead?)
This is what I've currently got. I pretty much hate seeing two
> 3) Include in postmaster but running on a separate thread (not process as
> Advantages: No extra binary. No extra process. Most integration.
> Disadvantages: Probably larger impact on postmaster code.
IMHO, the worst of all options.
I'm itching to throw this code somewhere :-)
Certain disclaimers and policies apply to all email sent from Memetrics.
For the full text of these disclaimers and policies see
pgsql-hackers-win32 by date
|Next:||From: Andrew Dunstan||Date: 2004-05-28 02:52:23|
|Subject: Re: win32 service code|
|Previous:||From: Andrew Dunstan||Date: 2004-05-27 21:56:53|
|Subject: Re: Re : Win32 binaries test / pg_dump problem|