PostgreSQL 8.4

By August 18, 2009Technical

Good news, everyone! PostgreSQL 8.4 is out, as of several weeks ago. Okay, this isn’t “new” news, but it’s not at all ungood, delay or otherwise. You can catch the feature list here, there’s some good stuff:

Of course the real trick is getting more of our customers to use the superior alternative, *le sigh*

As if you *needed* any further convincing to choose Postgres over Mysql, we’ve put together a little comparison for you that highlights some of the most obvious differences for you. 🙂

Oh yeah, using a Redhat OS? You’re short outta luck, you don’t get anything newer than 8.1.11 in the stock release – go use Debian, it’s better anyway. What are you missing out on? Plenty.


  • Morgan Tocker says:

    I don’t think your MySQL vs PostgreSQL is remotely fair.

    While you correctly cite limitations in MyISAM, most people with any traffic demands worth mentioning are almost exclusively using InnoDB, *and* InnoDB is transactional, fully ACID compliant, and also uses MVCC.

    It’s a myth that “SELECT queries are faster on MyISAM”. Table scans are faster on MyISAM, but because a filesystem cache is not normally as efficient as the InnoDB buffer pool, give it resources and InnoDB will often outperform on other SELECT statements. It will also scale better with concurrency.

    MySQL cluster is a completely different product, one that MySQL mainly targets at telcos, not web applications. It’s worth noting, but it’s not a pro – since it won’t necessarily retrofit well at all to most applications.

    I would expand on the point of postgres being “feature rich” – it’s true, it is. GIS support is something I’d rather use on postgresql for example.

    – Morgan

    • Barney Desmond says:

      Hi Morgan,

      Thanks for the comment. I’ll admit, we’ve got a bit of a bias against MySQL here at Anchor. 🙂 That said, most of ire probably stems from users falling into the MyISAM-by-default trap; we do know a number of great devs as well, and they’re clued in on the benefits of InnoDB.

      I’ve taken your notes on board and fleshed out the bullet points a bit more. Hopefully it presents a more-balanced point of view on things.