Graham Ashton

I too was having trouble connecting to Postgres after upgrading to 9.2 on Mountain Lion, but it all turned out to be do with my PATH variable.

You need to make sure that /usr/local/bin preceeds /usr/bin in your PATH on ML, as by default it doesn't (Mac's path_helper is run from /etc/profile and will put /usr/bin first). ML ships with Postgres client binaries, which can cause confusion when starting Postgres, initialising the db, and building client libraries (e.g. the pg gem).

I was wise to this so rebuilt the pg gem, but failed to do it in a shell that had /usr/bin before /usr/local/bin.

Uninstalling pg and then reinstalling it having set PATH up to use /usr/local solved all my issues, and I didn't need to create the old /var/pgsql_socket directory.

I hadn't seen --name-only. I tend to use this a lot instead (which also tells you how many lines were added/removed from each file):

git diff --stat HEAD^

I don't want to be a party pooper, but I'm really not sure this is a good idea.

It needlessly slows down page load speed (fairly significantly) and deviates from a browser's standard behaviour, neither of which are a great idea from a usability perspective.

The delay isn't just caused by the timeout; you're waiting for the DOM ready event before you start fading it in. Having said that, even if you changed the code so that you started the fade as soon as jQuery itself was loaded, I wouldn't be a fan.

Using heroku scheduler to do it is a nice touch. I use a bash script on a VPS...