From: | Glyn Astill <glynastill(at)yahoo(dot)co(dot)uk> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: postgre vs MySQL |
Date: | 2008-03-12 18:49:50 |
Message-ID: | 862959.64921.qm@web25815.mail.ukl.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
--- Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> 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.
>
I mean features being pulled into the enterprise release that haven't
had much time to be tested even in the community release.
___________________________________________________________
Rise to the challenge for Sport Relief with Yahoo! For Good
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-03-12 19:19:09 | Re: pain of postgres upgrade with extensions |
Previous Message | Joshua D. Drake | 2008-03-12 18:42:06 | Re: postgre vs MySQL |