MySQL 3.23.29 is pre-InnoDB (http://dev.mysql.com/doc/refman/4.1/en/innodb-in-mysql-3-23.html), so this database is not transactional, not ACIDic, and does not support row-level locking or foreign key referential integrity. At this point, MySQL lacked support for subqueries, UNIONs, VIEWs, and nearly everything else beyond basic CRUD. I bet I can design a program that interfaces flat data files so fast it makes any RDBMS pale in comparison. SQLite does that, and it's ACID compliant! Performance is not the only motivation for using an RDBMS. Data integrity and relational modeling are also big considerations. -- Brandon Aiken CS/IT Systems Engineer -----Original Message----- From: pgsql-general-owner@xxxxxxxxxxxxxx [mailto:pgsql-general-owner@xxxxxxxxxxxxxx] On Behalf Of Merlin Moncure Sent: Tuesday, October 10, 2006 1:56 PM To: PgSQL General Subject: [GENERAL] more anti-postgresql FUD http://www.zabbix.com/manual/v1.1/install.php in section PostgreSQL vs MySQL : [quoting] Regarding the choice between PostgreSQL and MySQL, MySQL is recommended for several reasons: * MySQL is faster recent benchmarks using ZABBIX clearly show that PostgreSQL (7.1.x) is at least 10 times slower than MySQL (3.23.29) Note: These results are predictable. ZABBIX server processes use simple SQL statements like single row INSERT, UPDATE and simple SELECT operators. In such environment, use of advanced SQL engine (like PostgreSQL) is overkill. * no need to constantly run resource-hungry command "vacuum" for MySQL * MySQL is used as a primary development platform. If you do use PostgreSQL, zabbix_server will periodically (defined in HousekeepingFrequency) execute command vacuum analyze. [done] anybody know these guys? this is right off the mysql anti-postgresql advocacy page. merlin ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster
