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

From Mike Mascari
Subject Re: fairly current mysql v postgresql comparison need for
Date
Msg-id 3E7F21CF.8020309@mascari.com
Whole thread Raw
In response to fairly current mysql v postgresql comparison need for advocacy  (merlyn@stonehenge.com (Randal L. Schwartz))
Responses Re: fairly current mysql v postgresql comparison need for  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Randal L. Schwartz wrote:
> 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?

VIEWS
Triggers
Rules
Subselects in target lists*
NUMERIC type of arbitraty precision
PL/pgSQL, PL/Tcl, PL/Perl, PL/Pythin
Multiversioning
User-definited data types, operators, and functions
Write-ahead logging
Partial indexes
Functional indexes
Rollbackable DDL (CREATE/DROP TABLE, etc.)
Absolutely 100% free

How's that, for a start?

*They apparently added subselects as of Jan of this year in FROM
and WHERE clauses. Docs don't mention target lists, they might
have implemented subselects in target lists though.

Mike Mascari
mascarm@mascari.com


pgsql-general by date:

Previous
From: "Shridhar Daithankar"
Date:
Subject: Re: fairly current mysql v postgresql comparison need for advocacy
Next
From: Tom Lane
Date:
Subject: Re: GiST: Need ideas on how to minimise data in a GiST index