You Say You Want a Revolution (or Dude, Where's My Database?)
Like a previous commenter said, it looks more like a highly opinionated rant than an actual useful article, more's the pity. Having said that, there are a few points that I sort of agree with the author. PostgreSQL is underrated, however it is 600% more scalable than the author is trying to make it. MySQL is not a true relational database system, but it is relational enough and ANSI SQL complient enough to make for a really useful tool. Both have got their place.
PostgreSQL does extremely well in situations where you would typically and traditionally would have used Oracle/Sybase/Informix, even if it does lack features that would be needed in an enterprise level RDMS. MySQL is excellent for web-based content management where transaction locking is not really needed. The speed and simplicity of MySQL counts heavily in it's favour here. Insofar sheer speed is concerned, PostgreSQL is doing some serious catching up - with each new release it's much faster. The current version actually rivals MySQL in terms of speed!
A few case studies:
Interbase has indexing problems, yes. However, there are ways to work around that without crippling your database so much that you cannot use it... Interbase is still one of the fastest RDMS systems around in terms of bulk data throughput, and that speed can be used to excellent effect in some situations. For instance, I use Interbase in a traffic logger system for an ISP to store IP flows measured with NeTraMet. Together they make a tight team! I tried PostgreSQL, but it did not quite make it. MySQL was too slow, which came as a big surprise to me. I have no intention (so far) to do actual tests to measure data throughput, so my experience with the above system is purely nuts 'n bolts, and the current arrangement works like a dream.
A number of different clients of my current employer has a number of franchised branches throughout the world. One client, a chicken-based fast food chain (not KFC! ;-) uses Linux and PostgreSQL with ISDN links as the backbone of their entire POS system. The ISDN links proved fast enough and cost effective too, since they saved a fortune in not having to have dedicated data links between stores. PostgreSQL replicates it's data blindingly fast to the company's central PostgreSQL server, proving the system to be incredibly scalable. An almost identical setup is used at another client, this time specialising in electronic equipment instead of chicken! ;-) They also open up branches at the rate of between 2 to 4 per week all over the world, and this mating of using PostgreSQL/ Linux/ISDN makes them incredibly competitive. Over here in Africa, PostgreSQL rules the roost!
I hope that the author would write another article that has some more useful content and post it here again. It is obvious that the author has extensive knowledge in database systems, and it would be wonderful if he can impart with some of that knowledge instead of doing it the way he did. The article was interesting noise, but unfortunately it is still noise. Pity.
For a really interesting comparison between MySQL and PostgreSQL, this time by the MySQL development team, download the MySQL source and read the "manual.txt" file that comes with it. You'll most probably be able to download just that file via CVSWeb somewhere, but it succeeds to be as objective as can be, even from the angle it has been written. If the author could have written an A vs B comparison like that, my life could have been a bit easier. Instead I've had to wast my time reading his piece, and write this comment. Life's a bitch... ;-)