postgres vs mysql conventional wisdom

From: Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com>
To: "pgsql-general(at)postgresql(dot)org General" <pgsql-general(at)postgresql(dot)org>
Subject: postgres vs mysql conventional wisdom
Date: 2010-04-01 11:21:49
Message-ID: 4BB481CD.8060209@cheapcomplexdevices.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On this first day of the month, I thought it might be interesting
to re-visit the conventional wisdom about postgres vs mysql.

Do these seem like fair observations?

Storage engines - Advantage Postgres for having far more available.

Postgre has such a wide range of storage engines to choose from --
ranging from whatever proprietary backend Yahoo uses,
to Fujitsu's proprietary storage engine; to PowerGres Plus's
proprietary storage engine; to Netezza's hardware accelerated
storage engine. In contrast, MySQL only has a few to choose from.

Broad Developer base - Advantage MySQL for having a more distributed team.

Postgres developers seem to be concentrated in a handful of companies.
After various acquisitions, MySQL developers are scattered to the four winds.

Large company support - Advantage Postgres for having larger companies support it.

Fujitsu ($46 billion 2009 revenue; 185,000
employees) much bigger than that little company that bought
whomever bought MySQL ($23 billion revenue; 73000 employees).

Any more?

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alban Hertroys 2010-04-01 11:27:06 Re: transaction control in pl/pgsql
Previous Message Dave Page 2010-04-01 11:17:47 Re: "1-Click" installer problems