fairly current mysql v postgresql comparison need for advocacy - Mailing list pgsql-general

From merlyn@stonehenge.com (Randal L. Schwartz)
Subject fairly current mysql v postgresql comparison need for advocacy
Date
Msg-id 86n0jk7r5y.fsf@red.stonehenge.com
Whole thread Raw
Responses Re: fairly current mysql v postgresql comparison need for advocacy  ("Shridhar Daithankar<shridhar_daithankar@persistent.co.in>" <shridhar_daithankar@persistent.co.in>)
Re: fairly current mysql v postgresql comparison need for  (Mike Mascari <mascarm@mascari.com>)
Re: fairly current mysql v postgresql comparison need for  ("scott.marlowe" <scott.marlowe@ihs.com>)
Re: fairly current mysql v postgresql comparison need for  ("scott.marlowe" <scott.marlowe@ihs.com>)
Re: fairly current mysql v postgresql comparison need for  ("scott.marlowe" <scott.marlowe@ihs.com>)
List pgsql-general
I'm getting beaten up by the mysql users around me because they claim
that MySQL 4.x with InnoDB solves all of the ACID problems, so Pg no
longer pulls clearly ahead.

Has anyone examined this closely so that I have some nice things to
say about Pg instead?

Also, has anyone done a MySQL 4.x v Pg 7.{2,3}.x comparison recently?
All of the comparisons I saw in google were older.

Thanks.

--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!

pgsql-general by date:

Previous
From: lists@petri.cc
Date:
Subject: plpgsql and setting array values.
Next
From: "Shridhar Daithankar"
Date:
Subject: Re: fairly current mysql v postgresql comparison need for advocacy