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

21–30 of 78 posts

Re: Heroku Postgres

#21

Post by jinushaun »

sgrove wrote: post #6

This is really exciting - the team behind this really cares about developers and their experience. They see a way things could be better, and regardless of technical difficulty, say, "why not?" Forking a db? Brilliant. Offload expensive task to passive followers? Obvious (in hindsight). Instant, brain-dead db provisioning? Of course. Personally, the only terrifying thing about this is that when Heroku releases someth…

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.

Re: Heroku Postgres

#22

Post by pvh »

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

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.

Re: Heroku Postgres

#23

Post by pvh »

swilliams wrote: post #12

It would seem that their acquisition by SalesForce hasn't slowed them down at all, in fact I'd go as far to say that they've been even more productive since that happened. I'm curious about how that whole process has gone; has SalesForce provided more support/funding/resources? Or just removed distractions and allowed them to focus on their product? Nice job Heroku.

Suffice it to say, any rumours of our demise were greatly exaggerated. So much more to come and yes, we are hiring, including for our Postgres team. (Resumes/github accounts/etc to jobs(at)heroku.com.)

Re: Heroku Postgres

#24

Post by pvh »

jinushaun wrote: post #21
sgrove wrote: post #6

This is really exciting - the team behind this really cares about developers and their experience. They see a way things could be better, and regardless of technical difficulty, say, "why not?" Forking a db? Brilliant. Offload expensive task to passive followers? Obvious (in hindsight). Instant, brain-dead db provisioning? Of course. Personally, the only terrifying thing about this is that when Heroku releases someth…

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...

Re: Heroku Postgres

#25

Post by boundlessdreamz »

pvh wrote: post #22
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

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.

Offer a public bounty ? Just the basic support for viewing data would be really helpful.

This is my biggest pain point while working with heroku.

Re: Heroku Postgres

#26

Post by hopeless »

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.

Re: Heroku Postgres

#27

Post by pvh »

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…

I would say that at this point you're right, we're probably not right yet for companies subject to HIPAA or PCI regulation.

The advanced Postgres datatypes are pretty much my favorite thing in the world. We use HStore internally all over the place, as well as some more exciting projects that we haven't said too much about yet. As I mentioned elsewhere in the thread, if you're interested in trying out some of those extensions, contact me directly.

Re: Heroku Postgres

#28

Post by pvh »

drewcrawford wrote: post #15

This is ridiculous, but I would love a REST interface to a SQL server. I do a lot of AppEngine work and although I love the datastore and write super-optimal queries, I would really love the ability to pull a SQL datasource in every once in awhile.

Check out the extremely cool HTSQL from Clark Evans!

Re: Heroku Postgres

#29

Post by pvh »

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 of each size.

Re: Heroku Postgres

#30

Post by samstokes »

firemanx wrote: post #18

Do they still limit the usage of user defined functions and contrib modules, or did that open up? I would love to use Heroku for some lightweight data warehousing that I've got going, but it's still pretty dependent on functions/sprocs for performance reasons. I looked for any more documentation about that, but the only official word I have from them in the past is the support ticket I filed last year stating that th…

We're running user-defined functions on Heroku right now (using a functional index on a custom hash function to get fast space-efficient queries on a string column of a large table).
Post reply on HN