From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Anony Mous <A(dot)Mous(at)shaw(dot)ca> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: FW: Postgres alongside MS SQL Server |
Date: | 2004-04-22 20:43:55 |
Message-ID: | 10102.1082666635@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Anony Mous <A(dot)Mous(at)shaw(dot)ca> writes:
> The reality of my situation is that the MS SQL Server may only reside on the
> same machine (Win2K server) until all data has been transferred from it to
> postgres, and then for maybe a month after that. Beyond that, postgres will
> be the only RDBMS on the box. It is for the transitional time where the
> concerns were raised. I am stuck, however, to running on top of a Win OS at
> the moment.
Hmm... I had taken your initial post to mean that you intended to run an
experimental Postgres server on the same box as your production server.
If you mean you intend to transition to using PG-on-Cygwin-on-Windows
as a production server, well, I don't think anyone around here will
recommend that as a good idea. That assemblage is not stable enough to
qualify as a production-grade database (bearing in mind that database
geeks have very high standards for "production grade" reliability).
You really ought to reconsider this.
In a year or three we may think that the currently-in-progress native
Windows port is stable enough to be used for production. But the
Cygwin port has never been intended as anything except a playpen for
application authors who wanted to write and test SQL code on their
Windows laptops.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | William Sweet | 2004-04-22 20:49:15 | Unicode encoding |
Previous Message | Federico Pedemonte | 2004-04-22 20:09:54 | Re: staggered query? |