On Mon, Dec 1, 2008 at 1:05 PM, Grzegorz Jaśkiewicz <[EMAIL PROTECTED]> wrote: > > > On Mon, Dec 1, 2008 at 8:00 PM, Steve Crawford > <[EMAIL PROTECTED]> 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 :)
I'd rather do the paritioning by hand and use slony and know it works than rely on the code that's doing all that in mysql. If your server crashes while updating a partitioned table, you could lose all the data in it. Replication can mysteriously just quit working with no errors or warning. Make your pick, half assed code that sometimes works, or postgresql. :) -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
