Re: postgre vs MySQL - Mailing list pgsql-general

From Bruce Momjian
Subject Re: postgre vs MySQL
Date
Msg-id 200803121835.m2CIZJR28938@momjian.us
Whole thread Raw
In response to Re: postgre vs MySQL  (Glyn Astill <glynastill@yahoo.co.uk>)
Responses Re: postgre vs MySQL  ("Joshua D. Drake" <jd@commandprompt.com>)
Re: postgre vs MySQL  (Glyn Astill <glynastill@yahoo.co.uk>)
List pgsql-general
Glyn Astill wrote:
>
> --- Greg Smith <gsmith@gregsmith.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@momjian.us>        http://momjian.us
  EnterpriseDB                             http://postgres.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

pgsql-general by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: FATAL: could not reattach to shared memory (Win32)
Next
From: Tom Lane
Date:
Subject: Re: ERROR: text search configuration "pg_catalog.english" does not exist