On Fri, 11 Jan 2002, Philip Molter wrote:

> The only downside you're going to find are the down/upsides of
> switching from MySQL to PostgreSQL.  The DBI interface won't change
> for you.  My personal experience between the two databases is that
> MySQL is easier to manage, easier to work with, and enjoys more
> active support from the Perl development community.  With MySQL's
> InnoDB tables, there's really not much that PostgreSQL has over
> MySQL except for very advanced, mostly proprietary extensions (with
> the exception of triggers, which are coming).  In everything I've
> coded, MySQL beats PostgreSQL hands-down for speed when both are
> configured properly.

Well, there are some neat features.  The table inheritance bits (really
sub- and super-types) is potentially really useful, and all RDBMS's
_should_ support this because it solves some rather common problems.  Of
course, I haven't used it myself (mostly because I haven't gotten Alzabo
around to supporting it).

Postgres also has views, which MySQL doesn't have.  I also don't know if
InnoDB+MySQL supports all constraints, or just referential integrity
contraints.

Also, MySQL's query optimizer is _really_ bad when it comes to complex
where clauses.  For example, a select like this:

  SELECT foo FROM Foo where indexed_col_1 = 'x' OR indexed_col_2 = 'y'

will not use either index.  That can be really bad.

>From what I've heard, the Postgres optimizer is quite a bit better.

Also, I'd be curious to see a speed comparison across a wide range of
operations (simple & complex selects, insert, update, delete) between
Postgres and InnoDB+MySQL.  Obviously, MySQL+MyISAM is faster.  But I'd be
surprised if InnoDB was significantly faster than Postgres.


-dave

/*==================
www.urth.org
we await the New Sun
==================*/

Reply via email to