Re: win32 service code - Mailing list pgsql-hackers-win32

From Claudio Natoli
Subject Re: win32 service code
Date
Msg-id A02DEC4D1073D611BAE8525405FCCE2B55F485@harris.memetrics.local
Whole thread Raw
In response to win32 service code  ("Magnus Hagander" <mha@sollentuna.net>)
Responses Re: win32 service code
List 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>

pgsql-hackers-win32 by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Re : Win32 binaries test / pg_dump problem
Next
From: Andrew Dunstan
Date:
Subject: Re: win32 service code