From: | Claudio Natoli <claudio(dot)natoli(at)memetrics(dot)com> |
---|---|
To: | 'Magnus Hagander' <mha(at)sollentuna(dot)net>, PgSql-Win32 <pgsql-hackers-win32(at)postgresql(dot)org> |
Subject: | Re: win32 service code |
Date: | 2004-05-28 00:06:50 |
Message-ID: | A02DEC4D1073D611BAE8525405FCCE2B55F485@harris.memetrics.local |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers-win32 |
My 2c,
> 1) Separate binary "pgservice.exe" that will CreateProcess() the
> postmaster.exe.
> 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
postmaster.exe/s running.
> 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.
IMHO, the worst of all options.
I'm itching to throw this code somewhere :-)
Cheers,
Claudio
---
Certain disclaimers and policies apply to all email sent from Memetrics.
For the full text of these disclaimers and policies see
<a
href="http://www.memetrics.com/emailpolicy.html">http://www.memetrics.com/em
ailpolicy.html</a>
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2004-05-28 02:52:23 | Re: win32 service code |
Previous Message | Andrew Dunstan | 2004-05-27 21:56:53 | Re: Re : Win32 binaries test / pg_dump problem |