Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Heroku Postgres

postgres.heroku.com

Post reply on HN
Print view View original

31–40 of 78 posts

Re: Heroku Postgres

#31

Post by pvh »

jvehent wrote: post #3

"Forget daily backups, Continuous Protection redundantly archives data to high-durability storage as it is written, ensuring that it is safe no matter what." I'm sorry, but daily backups are not only for high availability, but also for point in time recovery. What if $dev drops the user table by mistake ? Do they provide backup for that ?

We have found that large production databases do not appreciate having frequent full SQL dumps taken from them. We offer an automatic daily snapshot option because we believe that for a production database it's really not wise to take dumps more frequently than that, though there's nothing stopping you from rolling your own.

Re: Heroku Postgres

#32

Post by pvh »

hopeless wrote: post #26

I just realised that Heroku have a problem: when I looked at the page, and looked at the subdomain URL, I couldn't tell if this was a real offering or a fake app put up by someone else.

Yes, it's the real deal, just like blog.heroku.com and all our other services.

In order to reduce this ambiguity we are gradually moving towards placing user apps on a different domain; because we approach these kinds of issues very gradually this will probably take quite some time to fully complete, but as of today all new Cedar stack applications are hosted on herokuapp.com.

Re: Heroku Postgres

#34

Post by sandGorgon »

boundlessdreamz wrote: post #16

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

No can afford macbooks - something with Ubuntu please..

Re: Heroku Postgres

#35

Post by simonw »

olefoo wrote: post #4

Just a little usability nit, is the pricing per month, per year, lifetime? It's not clear from the pricing page, and I'm assuming it's per month, in which case it's reasonable, especially given the value added services being offered, especially the ability to fork the database and the automated creation of read slaves. It looks like a solid offering. It's probably not right for companies that are subject to HIPAA or…

That confused me too - the https://postgres.heroku.com/pricing page should definitely mention that it's per month. I'm also not clear on the difference between the Ronin and Fugu plans, both of which are 1.7 GB of RAM but one which is twice the price of the other.

Re: Heroku Postgres

#36

Post by pvh »

joevandyk wrote: post #2

Although they only let you create one database per plan, you can use schemas to emulate multiple databases. http://www.postgresql.org/docs/9.0/static/ddl-schemas.html

Just to clarify: You're almost right. You can, in fact, create multiple databases of any plan you please, but yes, within each of those databases you can use schemas to implement something akin to multiple databases without resource isolation, but with the ability to share data.

Re: Heroku Postgres

#37

Post by latortuga »

pvh wrote: post #29
andypants wrote: post #10

This is really awesome, just a few downsides (for me): I don't use postgres - I hope heroku expands this kind of service to more databases (although I don't think it's likely in the near future). The smallest database is also pretty expensive. I wouldn't mind a cheaper plan for less resources. Only being able to create one database of each size is just weird, especially if forking or following. Can anybody confirm th…

We are unlikely to offer MySQL at any point in the near future. We feel that across the board, Postgres has the best data robustness guarantees, the most powerful query optimizer, the strongest replication solutions, the most useful datatypes, and the greatest community driving, developing and supporting it. We hear you on the cheaper plan; watch this space. Last, there is no restriction on creating only one database…

Honestly when you list the merits of Postgres like that you sound like a used car salesman. "Of course you think you want that but really you want all of this." We all get that Postgres is great. Saying "no we won't implement a feature you, our customer, wants" like this just rubs me the wrong way.

Is there some technical reason that you can't offer both?

Re: Heroku Postgres

#38

Post by sgrove »

pvh wrote: post #24
jinushaun wrote: post #21

Earlier quoted context omitted.

When I read "forking" and "following" on there, it was a revelations: of course, that's so obvious! Those terms are much friendlier than "replication" or "master-slave". It describes the desired result, instead of the underlying technology.

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.

Re: Heroku Postgres

#39

Post by socratic »

latortuga wrote: post #37
pvh wrote: post #29

Earlier quoted context omitted.

We are unlikely to offer MySQL at any point in the near future. We feel that across the board, Postgres has the best data robustness guarantees, the most powerful query optimizer, the strongest replication solutions, the most useful datatypes, and the greatest community driving, developing and supporting it. We hear you on the cheaper plan; watch this space. Last, there is no restriction on creating only one database…

Honestly when you list the merits of Postgres like that you sound like a used car salesman. "Of course you think you want that but really you want all of this." We all get that Postgres is great. Saying "no we won't implement a feature you, our customer, wants" like this just rubs me the wrong way. Is there some technical reason that you can't offer both?

What would you like Heroku to do with a MySQL on EC2 offering that Amazon is not currently doing with their MySQL on EC2 offering (Amazon RDS)? They are both local, use the same underlying infrastructure, and have Heroku add-ons, no?

Presumably, their decision to only support Postgres is partly competition (many others provide MySQL on EC2), and partly technical. How would you justify the technical merits of the decision, without sounding "like a used car salesman"?

Re: Heroku Postgres

#40

Post by jasonjei »

jinushaun wrote: post #17
boundlessdreamz wrote: post #16

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 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.
Post reply on HN