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: 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: Fri, 28 May 2004 10:06:50 +1000
  • Message-id: <A02DEC4D1073D611BAE8525405FCCE2B55F485(at)harris(dot)memetrics(dot)local>

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>



Home | Main Index | Thread Index

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