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

From: Geoffrey <lists(at)serioustechnology(dot)com>
To: "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 20:43:01
Message-ID: 49344C55.3070108@serioustechnology.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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
.
.

:)

--
Until later, Geoffrey

Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.
- Benjamin Franklin

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2008-12-01 20:47:03 Re: Trigger before delete does fire before, but delete doesn't not happen
Previous Message Alvaro Herrera 2008-12-01 20:41:44 Re: Indexes on NULL's and order by ... limit N queries