Re: Database Performance?
От | Robert Berger |
---|---|
Тема | Re: Database Performance? |
Дата | |
Msg-id | A9255F60-23F8-11D6-AF47-000502B354E1@vtiscan.com обсуждение исходный текст |
Ответ на | Re: Database Performance? (Martijn van Oosterhout <kleptog@svana.org>) |
Ответы |
Re: Database Performance?
Re: Database Performance? Re: Database Performance? |
Список | pgsql-general |
This argument is out of date. MySQL currently supports transactions, foreign keys, and outer joins. (4.1 will support subselects) As for fault tolerance, MySQL has built in support for replication. A couple years ago I converted a project from MySQL to PostgreSQL because of MySQL's lack of features. I am now in the process of converting back to MySQL because of the performance improvements and replication. > > Be a little bit careful about benchmarks. Whether postgresql or > mysql is > faster depends on what you're doing. If all you want to do is the > occasional > insert and lots and lots of simple selects, mysql (or even grep) > will beat > postgres. If you want to do subselects, transactions, foreign > keys, outer > joins, fault tolerence or anything else that makes a database a > database, > mysql just can't do it. > > See if MySQL and PostgreSQL satisfy your business requirements and then > decide which one you want.
В списке pgsql-general по дате отправления: