If there is anyone from heroku reading, please pay some money to http://www.sequelpro.com/ developers to develop postgresql compatibility. All GUIs available on OS X for postgres are horrible
We love Sequel Pro and would love to see Postgres support. Unfortunately, nobody has stepped forward with a credible claim to do the work and the existing developers are all, for obvious reasons, much more familiar with MySQL. If anyone is interested in working on that patch, I would personally chip in to a promising effort, and I would encourage anyone else interested to do the same.
I'm a big fan of DBVisualizer (http://www.dbvis.com/), and have used it almost daily for ~6 years now on OSX. It's not a perfect OSX app (it's cross platform Java, but quite good looking for what that normally implies). Lots of power, doesn't crash, decent looking, and it works for pretty much every relational database out there (including MySQL, PostgreSQL, and Oracle).
I own a SequelPro license (as well as licenses for a couple of other non-free tools, RazorSQL and Querious) and I always come back to DBVisualizer.
I love using Sequel Pro for MySQL, but also wish it had support for SQLite and PostgreSQL. It's a great app and better than all the other OSX clients that I can find on the internet, including the non-free ones.
It's open source, so nothing's stopping anyone from adding support for other SQL servers.
I have contributed a little bit to Sequel Pro, and I'm a bit familiar with the codebase. Adding support for PostgreSQL is not trivial, a lot of MySQL is hardcoded into the user interface. There have always been many requests for PostgreSQL compatibility, but it would require A LOT of refactoring.
(Disclaimer: I haven't been involved much with SP for almost a year now, so possibly there has been progress in that time)
As one of the current Sequel Pro developers I can backup jabkobob on this one, it's not an easy task. It's not that we're ignoring the requests we get to add support for PostgreSQL or any other database system for that matter, it's simply a matter of time, of which most of the core devs don't have just now. We have a lot of plans around this area (as well as others) for the app, but it's going to take time.
I would pay good money for a postgresql client as superb as sequelpro, and I think a lot of other developers would. Someone is going to cash in on this gap if sequelpro don't beat them to it.
But it's kinda kickstarter in reverse since you have people wanting to give money but no one picked to do the work. It's a bounty.
I worked on and almost launched an open source bounty site a couple years ago. But the closer I got to launch the more I realized that I hadn't adequately solved all of the hard UX problems (mostly around a: picking who's going to work on it, trying to avoid both having two people separately do it due to know central coordination and having one person say "yeah, I'm going to do this!" and then not get around to it and hold the project back, and b: how to handle it when someone does technically address the bounty, but in a way that is unsatisfactory either because bounty-placers did not perfectly state their needs or because of poor quality.
Ugly on any non-Windows platform, too complicated for simple use (e.g. enter a query here and show me a result or show me a schema), etc. Well, just compare Sequel Pro screenshot with pgAdmin3 :)
Disclaimer: I actually like pgAdmin3, especially the visualized explain page.