Re: HEADS UP: Win32/OS2/BeOS native ports - Mailing list pgsql-hackers

From Jason Tishler
Subject Re: HEADS UP: Win32/OS2/BeOS native ports
Date
Msg-id 20020603131840.GA1020@tishler.net
Whole thread Raw
In response to Re: HEADS UP: Win32/OS2/BeOS native ports  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: HEADS UP: Win32/OS2/BeOS native ports - the 'BEST OPEN SOURCE database backend'  (Robert Schrem <robert.schrem@WiredMinds.de>)
GOODS - a sensational public domain database backend that deserves a SQL frontend  (Robert Schrem <robert.schrem@WiredMinds.de>)
List pgsql-hackers
Bruce,

On Sun, Jun 02, 2002 at 08:49:21PM -0400, Bruce Momjian wrote:
> mlw wrote:
> > Like I told Marc, I don't care. You spec out what you want and I'll write it
> > for Windows. 
> > 
> > That being said, a SysV IPC interface for native Windows would be kind of
> > cool to have.
> 
> I am wondering why we don't just use the Cygwin shm/sem code in our
> project, or maybe the Apache stuff; why bother reinventing the wheel.

Are you referring to cygipc above?  If so, they even one of the original
cygipc authors would discourage this:
   http://sources.redhat.com/ml/cygwin-apps/2001-09/msg00017.html

Specifically, Ludovic Lange states the following:
   > I really think the solution would be to start again from scratch   > another implementation, as was suggested. The
waywe did it was   > quick and dirty, the goals weren't to have production systems   > running on it but only to run
prototypes.So the internal design   > (if there is any) may not be adequate for the cygwin project.
 

However, Rob Collins has contributed a MinGW daemon to Cygwin to support
switching users, System V IPC, etc.  So, this code base may be a more
suitable starting point to satisfy PostgreSQL's native Win32 System V
IPC needs.

Jason


pgsql-hackers by date:

Previous
From: mlw
Date:
Subject: Re: HEADS UP: Win32/OS2/BeOS native ports
Next
From: Jason Tishler
Date:
Subject: Re: HEADS UP: Win32/OS2/BeOS native ports