Comparing MySQL and PostgreSQL 2

Mr. Jax writes "6 years ago Mr Poet submitted the story Comparing MySQL and PostgreSQL. Since then both databases have evolved to wherever they are today. Are the points raised 6 years ago still valid? What has changed? Are there other things to consider since then (e.g. licensing)?" This is certainly a valid question since both databases have had to evolve with the times. Have these applications been specialized to fit a particular niche market or are they both still strong competitors? What does the horizon look like for the development of these programs, especially considering the recent MySQL partnership with SCO?

Comments

Also

[TheRaven64]

I have been wondering, which is better, vi or emacs?

Re:Also

[cnettel]

Regarding potential for being a RDBMS, I would vote for emacs. I'll leave it to you to decide if that's a good thing...

Re:My point of view

[tangledweb]

So this is what passes for "Score 5: Informative" now?

Invent an imaginary version of postgres to compare to a real version of MySQL, then spout some fictional cons. In that case:

I'm using both, but mainly Postgres. From what I can tell:

Postgres 7.841
Pros:
- Supports african dialects such as Kaliharinese
- Adds extra features when it detects that the user is a Womble
- Compatible with IP/feline
Cons:
- Runs slowly if you try to quieten your hard drives with banana peels

MySQL 4.841
Pros:
- Written entirely by Ooompa Loompas
- Discourages the use of Perl
Cons:
- Supports animal testing. Drips of MySQL are places in the eyes of penguins to check for irritation.
- Shows signs of money contamination, which brings hippies out in a rash
- Does not support transactions.