Did not know this -- very cool. One of the only reasons I still use MySQL is that PostgreSQL would break some Drupal sites I deployed. I miss the ease of obta

Did not know this -- very cool. One of the only reasons I still use MySQL is that PostgreSQL would break some Drupal sites I deployed. I miss the ease of obtaining relational integrity under Postgres (although pgsql's EXPLAIN can be horrifying compared to MySQL's). Have scaled up to saturating an OC12 with Postgres (17 web servers) and doing 30 million hits/month with MySQL, so it's not like I care that much, but MySQL has a nasty tendency to piss me off in corner cases, and I'm getting tired of it. Definite pros and cons to both. I've seen people stick with (and patch) a particular point release ofMySQL (eg. 3.23 for AdWords at one point) just because the errors were consistent and they were no longer doing much to the schema. Never seen that happen with PostgreSQL. Jeremy Zawodny's tools (mytop, etc.) are invaluable if you have to get a MySQL shop to scale up (eg. without migrating a metric fuckload of existing SQL), btw.