Thursday, September 5, 2013

Postgres Shutdown and Startup

Before I start, I have to give a quick shout out to the folks over at the Illuminos IRC channel. I'm always disappointed when I pop into a channel looking for some advice and get crickets...for hours. Or, even worse, one half-hearted, disinterested reply that only goes so far as to inform you that you're "doing it wrong" and "should've done it like x". These folks were fast and spot on. I had no fewer than 4 people respond to my admittedly newb question, and it felt good. It felt right. It felt like what I expect open source to be about. So Kudos, folks. 

Let's get back to the matter at hand. Why was I even on the Illuminos channel, you might ask? You know how sometimes when you get a new member on your team and they're eager to bring in the technology they like? That happened. My new boss is a big ol' OpenSolaris fan, and proselytizes OpenIndiana wherever he can. I didn't find an OpenIndiana room but I did find an Illuminos room and since OI is built on Illuminos...well, that was where I went. Good thing too since my boss uses OI whenever he has an opportunity to, so when he was tasked with building out Postgres servers he chose OI instead of CentOS, which is used on every other box in our environment...I won't go into my concerns about trying to bring in a new OS into a production environment where only one person would have the expertise to set it up, maintain, and troubleshoot it... :)

So we have Postgres installed and started using it with our Hadoop cluster and ran into an issue in our staging environment.