Re: A newbie's opinion - postgres NEEDS a Windows binary!

first for clarity - i am NOT advocating that postgres be re-written
just to support win32. my initial point was to describe what would
need to be done if someone wanted to have a win32 native version.
i was sort of hoping it would be obvious that when i said that it
would take a complete rewrite to make it win32 native that people
on the list would understand what that means. for something like
postgres that would be a significant undertaking.

i use win32 at work and i do my personal coding on the cygwin binary
of postgres (soon moving to the mac osx version). my personal
production environment is a red hat linux machine with postgres. as
one of our fellow list members pointed out to me in a personal email,
you choose the tool that best fits your needs. if you _need_ to be
working in win32 with high-traffic then postgres is probably not for
you.

rjsjr

> PostgreSQL is built with a multi-process model, rather than a
> multi-threaded model such as MySQL.  The win32 platform cannot handle
> a multi-process model and probably never will (it would not be in
> MS's best interests nowadays anyway).  This is what makes a port a
> major difficulty and would set the PostgreSQL team back months to
> years in development time.  IMHO it is much more important to
> increase the functionality, stability, and speed of the *NIX version.
>  If you want to use PostgreSQL in a production environment then pick
> up a copy of Linux or FreeBSD.  These OSes a load easier to learn,
> use, and maintain than you win32-only people would think.  I am a
> win32 to Linux convert so you will have to trust me on this ;)  Plus,
> you can use any number of GUI tools that run on win32 to manipulate
> PostgreSQL: Access, Webmin, Putty, Winsql, phpPgAdmin.
>
> Brent
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
> http://geocities.yahoo.com/ps/info1
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>