Re: PostgreSQL a slow DB?
От | Chris Browne |
---|---|
Тема | Re: PostgreSQL a slow DB? |
Дата | |
Msg-id | 60psjokrhj.fsf@dba2.int.libertyrms.com обсуждение исходный текст |
Ответ на | Re: PostgreSQL a slow DB? (<ebcorder@rockwellcollins.com>) |
Список | pgsql-novice |
sid.murthy@gmail.com ("Sid Murthy") writes: > MySQL 5 is quickly catching up. Maybe someone can elaborate on the > advantages of Postgres over MySQL 5? The trouble with the "catching up" that MySQL has been doing is that it is coming at the "benefit" of adding checkbox points [Features X, Y, and Z now supported] at the cost that they are adding "gotchas" <http://sql-info.de/mysql/gotchas.html> much faster than they are eliminating them. For instance, it's "wonderful" that they have added built-in replication. At least, it's wonderful until you see the pretty enormous set of caveats. <http://dev.mysql.com/doc/refman/5.0/en/replication-features.html> <http://dev.mysql.com/doc/refman/5.0/en/stored-procedure-logging.html> Not all of those issues have yet entered the Gotchas list... The trouble, in effect, is that they are "slapping on" new features as opposed to "designing in" new features. Generally speaking, if you look at PostgreSQL features that get added, they are "designed in," and can be expect to work pretty well anywhere. The same does not appear to be true when features are added to MySQL. -- (format nil "~S@~S" "cbbrowne" "ntlug.org") http://www3.sympatico.ca/cbbrowne/rdbms.html Rules of the Evil Overlord #161. "I will occasionally vary my daily routine and not live my life in a rut. For example, I will not always take a swig of wine or ring a giant gong before finishing off my enemy." <http://www.eviloverlord.com/>
В списке pgsql-novice по дате отправления: