From: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | pgsql-advocacy(at)postgresql(dot)org, David Fetter <david(at)fetter(dot)org>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, Kaare Rasmussen <kaare(at)jasonic(dot)dk> |
Subject: | Re: PostgreSQL vs. SQL Server, Oracle |
Date: | 2006-10-12 19:50:25 |
Message-ID: | 20061012195024.GX28647@nasby.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy |
On Wed, Oct 11, 2006 at 10:55:33PM -0700, Josh Berkus wrote:
> David,
>
> > Then they should have mentioned it. PostgreSQL has real issues, and
> > if they'd mentioned any one of these, it would have been reasonable.
> > Instead, these guys chose to spread the FUD around and call PostgreSQL
> > a toy.
>
> That's not how I read the article. They recommended PostgreSQL for "edge"
> applications, which is the conventional opinion on Open Source databases.
> From my perspective, it's a positive article for us: "Try PostgreSQL, you
> might like it."
Not only that, but I think the very last answer really hit the nail on
the head when it comes to MySQL and PostgreSQL: there's no need to take
MySQL's trade-offs for even your light-weight applications.
The reality is, very few companies are willing to bet their a..erm,
donkey ;) on PostgreSQL... yet. Remember that most of the people at a
level that can make that decision have probably barely even heard about
PostgreSQL, so it's no surprise they're not ready to bet the farm on it.
Given time and sucessful deployments in less-critical areas, this will
change. Especially if the big 3 keep their pricing where it is...
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
From | Date | Subject | |
---|---|---|---|
Next Message | David Fetter | 2006-10-12 20:25:16 | Re: PostgreSQL vs. SQL Server, Oracle |
Previous Message | Josh Berkus | 2006-10-12 05:55:33 | Re: PostgreSQL vs. SQL Server, Oracle |