Re: Monty on MySQL 5.1: "Oops, we did it again"

From: justin <justin(at)emproshunts(dot)com>
To: Geoffrey <lists(at)serioustechnology(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Monty on MySQL 5.1: "Oops, we did it again"
Date: 2008-12-01 22:11:10
Message-ID: 493460FE.1060105@emproshunts.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Geoffrey wrote:
> Grzegorz Jaśkiewicz wrote:
>>
>>
>> On Mon, Dec 1, 2008 at 8:00 PM, Steve Crawford
>> <scrawford(at)pinpointresearch(dot)com
>> <mailto:scrawford(at)pinpointresearch(dot)com>> wrote:
>>
>>
>> http://monty-says.blogspot.com/2008/11/oops-we-did-it-again-mysql-51-released.html
>>
>>
>> All interesting, but especially the part about half-way down under
>> the heading "So what went wrong with MySQL 5.1 ?" - must-read for
>> anyone involved in selecting a database.
>>
>>
>> well, at least they have replication and partitioning built in. How
>> reliable it is, is completely another story - but still, they are a
>> step ahead in that regard. Now I know why Tom Lane doesn't have a
>> blog :)
>
> Actually, he has a couple of them:
>
> pgsql-general(at)postgresql(dot)org
> admin(at)postgresql(dot)org
> .
> .
>
> :)
>

I'm very happy and proud to use Postgresql as the developers working on
Postgresql deliver a quality product, not claim its quality.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Greg Smith 2008-12-01 22:20:36 Re: Monty on MySQL 5.1: "Oops, we did it again"
Previous Message Tom Lane 2008-12-01 21:28:54 Re: Indexes on NULL's and order by ... limit N queries