Need concrete "Why Postgres not MySQL" bullet list

Folks,

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.
Examples:

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