pvh

15 ms·

121.
by pvh 15y ago
Last time I looked it came with 8.4; I would highly recommend installing 9.1. A lot of awesome things have come out in the last few years.
122.
by pvh 15y ago
Good idea!
123.
by pvh 15y ago
If you can make a dataclip, you have access to the database. We've audited it for privilege escalation and put some simple shooting-yourself-in-the-foot protection in, but if you REALLY REALLY want to screw yourself over you can probably fi
124.
by pvh 15y ago
Seconded!
125.
by pvh 15y ago
Looking over the list here, I'd call out a few specific things that are important to me: * HStore, the key-value store column type * PGXN, still new, but going to change the world * Replication that Actually Works For Real No Kidding. * Win
126.
by pvh 15y ago
Congrats to the team for a really exciting release. We can't wait to ship it here at Heroku.
127.
by pvh 15y ago
PostGIS is currently in a pilot phase. If you're serious, please contact me as described elsewhere on this thread.
128.
by pvh 15y ago
As of today, we only charge for the time you use. I don't imagine we'd ever need to change that, but never is a long time.
129.
by pvh 15y ago
Not yet.
130.
by pvh 15y ago
Hmm, this would make a good blog post. I'll draft something up.
131.
by pvh 15y ago
Actually, Postgres WAL support helps mitigate this reasonably well, and a well tuned application has something like a cache hit rate of >99% during normal operation. That said, yes, EBS can have unstable performance. We monitor for seve
132.
by pvh 15y ago
We've done a lot of tuning focused on web applications already, our experience is that mostly people with problems just need to add an index. Performance depends on where you are querying from. We've found that if you are inside EC2 network
133.
by pvh 15y ago
No plans to support untrusted languages as yet. Too many foot-guns built into that. You couldn't even believe some of the evil, insane things that we've done with that. Trusted languages are far more likely. This one looks really, really co
134.
by pvh 15y ago
Sorry, I thought you wanted to know why we chose Postgres over MySQL. Those are the specific features I think that make Postgres a better choice for both use as my day-to-day database and why we chose Postgres over MySQL for building a data
135.
by pvh 15y ago
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 isolati
136.
by pvh 15y ago
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 gradual
137.
by pvh 15y ago
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
138.
by pvh 15y ago
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 datatyp
139.
by pvh 15y ago
Check out the extremely cool HTSQL from Clark Evans!
140.
by pvh 15y ago
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 th
141.
by pvh 15y ago
If you had any idea how long it took to get that language right...
142.
by pvh 15y ago
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.)
143.
by pvh 15y ago
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
144.
by pvh 15y ago
Our production service has always supported UDFs, though the free sandbox service does not. Unfortunately, Postgres makes it difficult to install extension modules without superuser. That said, we've wanted to support contrib modules for ag
145.
by pvh 15y ago
I'm a huge fan of Procfile. When I use a Procfile app, I know that regardless of the language or the configuration of processes, workers, clocks, or what-have-you, I can always get it up and running with a single `foreman start`.
146.
by pvh 15y ago
Achievement Unlocked: Switched to Pivotal (80GP)
147.
by pvh 15y ago
Hey Jedberg, if you guys aren't already rolling your own, check out fdr's WAL-E tool. It bounces postgres write-ahead logs off S3 and goes great with the new PG9 replication. https://github.com/heroku/WAL-E
148.
by pvh 16y ago
Way ahead of you. The tricky part is being able to bootstrap if the service crashes. It's pretty neat being able to basically provide artificial respiration for your web app in an emergency.
149.
by pvh 16y ago
I'm already building an addon as a Heroku app. Of course, I work for Heroku, so it probably doesn't count.
150.
by pvh 17y ago
Just change the name. Not a big deal.

More ›