> Claudio Natoli wrote:
> > * Users already have a postgres solution for Win32. It is called Cygwin
> > w/ > cygipc. Sure, it is not the most stable solution, but, IMHO,
> > that's not what prevents people from using it; it is the need to
> > install yet-another bit of software to support Postgres. If we want
> > to take the fight to MySQL, again IMNSHO, this is not the way to
> > proceeed.
> I don't use it because I don't feel it is stable and the write
> performance is not very good. Also, the ipc-daemon sometimes crashes
> which is a big PITA.
Exactly why we don't (can't!) use it in production. I was referring more to
the person we want to win over to Postgresql; the person who'll download the
Postgres Win32 binaries, and make a decision within 5 minutes as to whether
to keep playing with it, or whether to ditch it forever.
As Tom has said, if we can redistribute the components "invisibly" (which
the existing license appears to be completely silent on), great, and it is
something we might want to look at, IMHO, at a later date. Otherwise, forget
Aside: Looking *much* further ahead, with all Microsoft OS moving to the NT
subkernel, and this latest announcement that SFU is now available at no
cost, I think it is pretty clear that, sooner or later, SFU is going to work
its way into future MSFT OS releases as distributed. Whether this ultimately
keeps people using their OS, or makes it easier for people to switch, well,
time will tell...
> Plus, the win32 is so close to completion I can almost taste it... :)
Certain disclaimers and policies apply to all email sent from Memetrics.
For the full text of these disclaimers and policies see
pgsql-hackers-win32 by date
|Next:||From: Merlin Moncure||Date: 2004-01-16 13:38:36|
|Subject: Re: Win32 signal code - first try|
|Previous:||From: Tom Lane||Date: 2004-01-15 22:07:49|
|Subject: Re: Microsoft releses Services for Unix |