News for hackers. Stuff that matters.
Re:Amazon RDS for PostgreSQL by jacques_chester on Friday November 15, 2013 @12:34AM (#6737923)
I run a small Wordpress network. MySQL's insistence on going to disk for joins on tables with a TEXT field (even if the query doesn't touch those fields) is probably the major performance bottleneck.
Re:Amazon RDS for PostgreSQL by e12e on Friday November 15, 2013 @11:59AM (#6740506)
Ouch. Thanks for the explicit heads-up. I generally stay with PostgreSql, but I honestly thought most of these things were "fixed" in recent versions of MySQL (and assumed my subconcious dislike of MySql was at least partly irrational/rooted in Ancient and Outdated Lore). I guess not:

http://dev.mysql.com/doc/refman/5.7/en/internal-temporary-ta...

I'm not sure what the status of TEXT-fields are in mariadb:

https://mariadb.com/kb/en/optimizing-string-and-character-fi...

Re:Amazon RDS for PostgreSQL by jacques_chester on Friday November 15, 2013 @08:59PM (#6743245)
> Thanks for the explicit heads-up.

It took me a long term to learn this one. I suppose if I'd read the MySQL docs from cover to cover I would've found it earlier.

One other problem that popped up was ignoring indexes on tables with TEXT fields during joins, which was a planner weakness. I understand it was fixed in 5.6; I'm waiting for the Percona version to stabilise before I upgrade.

Re:Amazon RDS for PostgreSQL by eli on Friday November 15, 2013 @05:47PM (#6742670)
I tried MariaDB about a year ago and it had the same problem. It's possible it's been fixed since. I personally prefer the Percona fork of MySQL, which has some performance tweaks yet is basically a 100% drop-in replacement.