From: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
---|---|
To: | "PgSql-Win32" <pgsql-hackers-win32(at)postgresql(dot)org> |
Subject: | win32 service code |
Date: | 2004-05-27 19:10:58 |
Message-ID: | 6BCB9D8A16AC4241919521715F4D8BCE1716A6@algol.sollentuna.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers-win32 |
Hi!
Last I spoke with Claudio, he was still waiting for some reactions from
others than me on how we want the service code. So I figured I'd post a
recap of the options we have. I've added some advantages/disadvantages,
but those are my thoughts only. There are sure to be others.
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.
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?)
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.
As said, I've probably missed some in adv/disadv, but I think I got all
our options.
Thoughts?
//Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2004-05-27 19:28:50 | Re: win32 service code |
Previous Message | Greg Copeland | 2004-05-27 19:10:10 | Re: win32 port getting popular |