Technology has come a long way, hasn’t it? Fortunately (or unfortunately) for me, we could never afford braces while I was growing up. As a consequence, my mouth contains unspeakable horrors, a jumbled mess of crooked trolls, crowding haphazardly around a fresh carcass. I’m not kidding. While my smile won’t crack any mirrors, I have the overbite of a horse and the canines of a timber wolf. And like an unbalanced chair, my wobbly bite has ushered in periods of intense jaw cramps over the last few years.
A few months ago, Greg Smith of PostgreSQL fame suggested I submit a proposal to the new Postgres Open conference here in Chicago. Some of us residents of the Midwest have long waited for a PostgreSQL-related conference of our very own, and now the glorious day has finally arrived. I was asked to submit proposals to other conferences, but the travel involved quickly put me off; now I can be lazy and still help spread The Word.
I just installed Android Gingerbread (2.3) on my HTC Droid Eris. To understand the significance of this little achievement, we need to examine the wonderful world of smartphones, and why the market insists on doing a half-assed job.
The Eris was released November 6th, 2009. In the phone world, especially now that the smartphone market is heating up, this is somewhat ancient. It’s second-generation in a fifth and sixth generation world.
Ah, query hints. For all those times when the database isn’t doing what you want, they’re a useful tool for forcing the query optimizer to perform your bidding. But in this case, not only is the road to Hell paved with good intentions, it’s paved with a frictionless slide directly into a wood chipper that empties handily into an active volcano. With query hints, be careful what you wish for, because—to the detriment of all you hold dear—you just might get it.
Ok, so I’ve already corrected gaudy and horrible behavior part and parcel with default PostgreSQL installs, but what about that… other open-source SQL database? Is it wrong too? Sure is!
Fixing Your Damn Server Again My fake system still has 8GB of RAM, but we’ll be using more of it for a MySQL install. Why? Because MySQL’s planner makes different assumptions about memory allocation than PostgreSQL. Remember sysctl.conf? Put this in there:
