pvh

13 ms·

91.
by pvh 14y ago
You could always use Heroku Postgres. Our whole reason to exist is to ensure you can work fearlessly with your data. At this point, I think running your own data infrastructure is like having a generator in your garage instead of using the
92.
by pvh 14y ago
Here's a little teaser: https://github.com/will/datascope
93.
by pvh 14y ago
We give talks some times, and we're always happy to answer questions if you've got 'em. We open source stuff sometimes too, if we think it might be generally useful.
94.
by pvh 14y ago
Thanks a lot! We've come a long way since then - forks, followers, dataclips, extensions, new plans, new versions... Man, actually it kind of terrifies me to think of it all.
95.
by pvh 14y ago
At Heroku we call it Postgres in all things and at all times unless we're referring to official community stuff. It's a much better name, and it's the original name, and I hope some day it will be the only name.
96.
by pvh 14y ago
Yes, wouldn't it be cool if you could fork an entire running app?
97.
by pvh 14y ago
We haven't announced cross-region followers. When we announce it, there will be an announcement. This is an internal feature we've been using for a while that we thought our customers might appreciate access to under the circumstances.
98.
by pvh 14y ago
For the record, Heroku doesn't affect your ability to use triggers. It's possible our ancient "shared database" infrastructure simply didn't support it, but the new starter tier plans certainly do.
99.
by pvh 14y ago
People often ask us at Heroku -- why Postgres? The short answer is: we needed to do something, and it's the best.
100.
by pvh 14y ago
I absolutely disagree. Drop-in portability between databases is an operational myth for any production application anyway. Whether you're using Postgres, Riak, Mongo or Oracle, you're going to have to do a lot of work to change your databas
101.
by pvh 14y ago
I don't believe so, no.
102.
by pvh 14y ago
Oh, you don't need to use Heroku to take advantage of Heroku Postgres -- it's available as a standalone service.
103.
by pvh 14y ago
Well, if the time it takes you to contort your application to work around our row limits is worth less to you than $9/mo, you're probably in need of both technical and financial advice.
104.
by pvh 14y ago
Hm. If you must do that, remember Postgres is guilt-free-SQL, so don't use a varchar, use the array type. http://www.postgresql.org/docs/9.1/static/arrays.html
105.
by pvh 14y ago
Two quick points. First, please don't abuse the free databases. Second, the free "dev" plan does not support fork or follow, nor do we plan to support those features on that plan in the near future.
106.
by pvh 14y ago
Heroku doesn't charge for storage. Our pricing model is based on the amount of data you can have cached in memory.
107.
by pvh 14y ago
If the problems you're talking about are installation related (and you're on a Mac), we've got your back: http://postgresapp.com
108.
by pvh 14y ago
Most of our beta-testers have been using it just fine. We had one unlucky soul who encountered several pernicious bugs over a long period, but at this point I think they're all sewn up.
109.
by pvh 14y ago
Many of us are reading. We'll look into increasing the contrast.
110.
by pvh 14y ago
Crane is not intended to be the plan that will fill the role of the existing $15/mo database. We're still working on that one.
111.
by pvh 14y ago
I've been agitating for an API that would allow developers to build their own query languages on top of Postgres alongside of SQL. Some day.
112.
by pvh 14y ago
I wouldn't expect too much from XC in 1.0 state. When I last looked in on it there was still a ton of work to do before it was really operationally ready to put in production. I'd love to hear from anyone who has managed to deploy the beta.
113.
by pvh 14y ago
Hey, that's a thing we made. Happy to answer questions if you have any.
114.
by pvh 14y ago
This is my least favorite MySQL misfeature, and it's something that users migrating FROM MySQL often rely on in their application and get surprised/angry when they encounter errors rather than silent successes.
115.
by pvh 14y ago
Hitoshi Harada and Andrew Dunstan are currently working on making it ready to put into production. Also, he's working on backporting the new JSON datatype to 9.1 as an extension!
116.
by pvh 14y ago
Counterpoints: - using pg arrays is awesome, and for many access patterns is more performant and equally normalized - MySQL is mostly quite correct, though I disagree with some of the implicit casting of values to integers and some nuances
117.
by pvh 14y ago
* Check out wal-e ( https://github.com/heroku/wal-e ), we wrote it and we manage 250k postgres databases with it. :) * libpq does basically suck, but go has a pretty great native implementation. suggestions are welcome for improvement, patc
118.
by pvh 14y ago
Etsy did. I don't think it was a good decision and I think the reasons they did had more to do with resetting from some bad architecture decisions, but they're the example I know of. http://codeascraft.etsy.com/2011/09/28/scaling-etsy-what
119.
by pvh 14y ago
That method doesn't give you a running Postgres; you still need to configure the cluster yourself.
120.
by pvh 14y ago
"After all, if you have enough money you can work on any project you want." Well, not Half-Life 3. To do that, you have to take a job at Valve.

More ›