Re: Monty on MySQL 5.1: "Oops, we did it again" - Mailing list pgsql-general

From Geoffrey
Subject Re: Monty on MySQL 5.1: "Oops, we did it again"
Date
Msg-id 49344C55.3070108@serioustechnology.com
Whole thread Raw
In response to Re: Monty on MySQL 5.1: "Oops, we did it again"  ("Grzegorz Jaśkiewicz" <gryzman@gmail.com>)
Responses Re: Monty on MySQL 5.1: "Oops, we did it again"  (justin <justin@emproshunts.com>)
Re: Monty on MySQL 5.1: "Oops, we did it again"  ("Grzegorz Jaśkiewicz" <gryzman@gmail.com>)
List pgsql-general
Grzegorz Jaśkiewicz wrote:
>
>
> On Mon, Dec 1, 2008 at 8:00 PM, Steve Crawford
> <scrawford@pinpointresearch.com <mailto:scrawford@pinpointresearch.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@postgresql.org
admin@postgresql.org
.
.

:)

--
Until later, Geoffrey

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

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Trigger before delete does fire before, but delete doesn't not happen
Next
From: Maxim Boguk
Date:
Subject: Re: Indexes on NULL's and order by ... limit N queries