Live data from Hacker News

Heroku Postgres

postgres.heroku.com

51–60 of 78 posts

Re: Heroku Postgres

#51
post #38
post #24

Earlier quoted context omitted.

If you had any idea how long it took to get that language right...

I'd be curious to hear the alternatives, and the overall process used to arrive at the current language.

I seem to remember the term "manumission" being floated around during the beta process... :)

Re: Heroku Postgres

#53

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

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.

Re: Heroku Postgres

#54
post #46
post #9

Earlier quoted context omitted.

You can set up Point In Time Recovery (PITR), and replay recovery logs. It's not clear from Heroku's pages whether their solution is set up that way.

It sounds like their solution is set up that way. From https://postgres.heroku.com/#protect : "Every change to your data is written to write-ahead logs, which are shipped to multi-datacenter, high-durability storage. In the unlikely event of unrecoverable hardware failure, these logs can be automatically 'replayed' to recover the database to within seconds of its last known state."

It sounds like their solution is set up that way.

I think the question is whether the customer will be able to perform a point in time recovery, and what the size and resolution of the backlog is.

Re: Heroku Postgres

#55
post #38
post #24

Earlier quoted context omitted.

If you had any idea how long it took to get that language right...

I'd be curious to hear the alternatives, and the overall process used to arrive at the current language.

Hmm, this would make a good blog post. I'll draft something up.

Re: Heroku Postgres

#56
post #54
post #46

Earlier quoted context omitted.

It sounds like their solution is set up that way. From https://postgres.heroku.com/#protect : "Every change to your data is written to write-ahead logs, which are shipped to multi-datacenter, high-durability storage. In the unlikely event of unrecoverable hardware failure, these logs can be automatically 'replayed' to recover the database to within seconds of its last known state."

It sounds like their solution is set up that way. I think the question is whether the customer will be able to perform a point in time recovery, and what the size and resolution of the backlog is.

Not yet.

Re: Heroku Postgres

#58
This is cool, seems to have a pretty fair price structure. I still don't understand their shared database pricing. 5mb for free, then $15 for 20gb. I need like 100 megs for 5 bucks.

Re: Heroku Postgres

#59
post #44

Earlier quoted context omitted.

What's wrong with pgAdmin ?

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.

PgAdmin3 on Ubuntu here: gorgeous!

Re: Heroku Postgres

#60

Earlier quoted context omitted.

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.

Is Navicat OK? I've been using it for a while simply because it was one binary that did SQLite, MySQL, Oracle, MS-SQL, and PgSQL.

I've used Navicat Premium with Postgres and have had no issues. Pricey, but it works.
Post reply on HN