| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | Shashank <shashank(dot)tripathi(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: More grist for the PostgreSQL vs MySQL mill |
| Date: | 2007-01-21 18:36:05 |
| Message-ID: | 28092.1169404565@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> Shashank wrote:
>>> It seems MySQL just dropped the ball on
>>> the free version of their product, and it
>>
>> Not sure what you mean. I can download their latest versions without
>> any trouble.
> In contrast to the MySQL Enterprise Server, which receives both monthly
> rapid updates and quarterly service pack releases, there is no specific
> schedule for when a new version of the MySQL Community Server is
> released.
Not only that, but mysql has repeatedly issued community updates that
were actively *broken* --- something like four of the last seven minor
5.0.x updates were not pushed out by Red Hat because they broke ABI
compatibility with the prior version of libmysqlclient. I get the
strong impression that those guys are in over their heads in terms of
their ability to manage their software, or at least their ability to
manage two separate release streams.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Johnson | 2007-01-21 19:51:45 | Re: More grist for the PostgreSQL vs MySQL mill |
| Previous Message | Tom Lane | 2007-01-21 18:21:34 | Re: Using transactions with plpythonu |