From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Glyn Astill <glynastill(at)yahoo(dot)co(dot)uk> |
Cc: | Greg Smith <gsmith(at)gregsmith(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: postgre vs MySQL |
Date: | 2008-03-12 18:35:19 |
Message-ID: | 200803121835.m2CIZJR28938@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Glyn Astill wrote:
>
> --- Greg Smith <gsmith(at)gregsmith(dot)com> wrote:
>
> > If you look at the link I passed along before, you'll see the
> > difference
> > with MySQL is that they've been abusing their customers with minor
> > point
> > releases that try to add new features. Instead some of these
> > introduce
> > functional regressions, which often hang around for a whole long
> > longer
> > than two days after being noticed (this isn't even considering the
> > delays
> > before those fixes make their way back into the open source
> > product, some
> > only even go to paying customers).
>
> This is something I noticed too when looking at MySQL and postgres.
> The frequency of bug fixes and features, some coming over pretty
> quickly from the community release of MySQL scared me.
MySQL has incentives to _not_ make their community release
production-quality.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Lincoln Yeoh | 2008-03-12 18:35:39 | Re: postgre vs MySQL |
Previous Message | Bruce Momjian | 2008-03-12 18:34:06 | Re: FATAL: could not reattach to shared memory (Win32) |