Skip site navigation (1) Skip section navigation (2)

Need concrete "Why Postgres not MySQL" bullet list

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-advocacy(at)postgresql(dot)org
Subject: Need concrete "Why Postgres not MySQL" bullet list
Date: 2003-08-20 15:39:28
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-advocacypgsql-generalpgsql-hackers

I need someone to prepare a standard response for me to send out to inquiries 
on this topic.  I get them a lot.

What I'd like is a factual, non-perjorative list of the things which 
PostgreSQL and the PostgreSQL project have that MySQL does not, with a little 
bit of explanation by each.   Where links can be provided, please do so.  

PROCEDURES:  Postgres supports stored procedures (as functions) allowing 
programming in the database for the many tasks which are far more efficient, 
consistent, and secure done there.   Procedures may be written in any of nine 
different languages, currently, with two more in development.  MySQL does not 
support procedures at all.

TRANSACTIONS:  blah, blah, blah.   MySQL has just begun offering transactions 
this year, and their solution is largely untested, slow, and suffers from 
complications with the many different "table types".  PostgreSQL's MVCC 
transaction support, on the other hand, has been in use in production in 
numerous environments for over six years.

Can anyone do this?

Josh Berkus
Aglio Database Solutions
San Francisco


pgsql-hackers by date

Next:From: Jan WieckDate: 2003-08-20 16:11:38
Subject: Re: Buglist
Previous:From: Bruno Wolff IIIDate: 2003-08-20 14:56:27
Subject: Re: Buglist

pgsql-advocacy by date

Next:From: Josh BerkusDate: 2003-08-20 15:41:12
Subject: Re: Draft #7: yet more dramatic changes
Previous:From: Josh BerkusDate: 2003-08-20 15:25:47
Subject: Re: Draft #7: yet more dramatic changes

pgsql-general by date

Next:From: Stephan SzaboDate: 2003-08-20 15:58:57
Subject: Re: Buglist
Previous:From: scott.marloweDate: 2003-08-20 15:16:19
Subject: Re: Buglist

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group