From: Jeffrey Tenny <jeffrey.tenny@comcast.net>
To: pgsql-performance@postgresql.org
Subject: Re: Need help to decide Mysql vs Postgres
Date: Mon, 06 Jun 2005 11:51:22 -0400
Message-ID: <42A470FA.1080001@comcast.net> (raw)
Re: your JDBC wishes: Consider IBM Cloudscape (now Apache Derby) too,
which has an apache license. It's all pure java and it's easy to get going.
As to MySql vs Postgres: license issues aside, if you have
transactionally complex needs (multi-table updates, etc), PostgreSQL
wins hands down in my experience. There are a bunch of things about
MySQL that just suck for high end SQL needs. (I like my subqueries,
and I absolutely demand transactional integrity).
There are some pitfalls to pgsql though, especially for existing SQL
code using MAX and some other things which can really be blindsided
(performance-wise) by pgsql if you don't use the workarounds.
MySQL is nice for what I call "raw read speed" applications. But that
license is an issue for me, as it is for you apparently.
Some cloudscape info:
http://www-306.ibm.com/software/data/cloudscape/
Some info on pitfalls of MySQL and PostgreSQL, an interesting contrast:
http://sql-info.de/postgresql/postgres-gotchas.htmlhttp://sql-info.de/mysql/gotchas.html
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: jeffrey.tenny@comcast.net
Subject: Re: Need help to decide Mysql vs Postgres
In-Reply-To: <42A470FA.1080001@comcast.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox