Re: Database Performance?

From: Robert Berger <rwb(at)vtiscan(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Database Performance?
Date: 2002-02-17 22:49:55
Message-ID: A9255F60-23F8-11D6-AF47-000502B354E1@vtiscan.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Andrew Snow 2002-02-17 23:02:07 Re: Database Performance?
Previous Message Kym Farnik 2002-02-17 22:09:40 Re: Question: Who's Using Postgres