Any chance of PL/python or similar?
I guess I'm probably one of like three users of PL/python, especially since it's untrusted. Worth a check, though!
Heroku Postgres
41–50 of 78 posts
Re: Heroku Postgres
#42Is this still using the EBS RAID that you guys mentioned in a blog post a while ago? If so, how do you avoid any slow I/O requests (which plague EBS) stalling all I/O to the volume?
Re: Heroku Postgres
#43Earlier 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?
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 database service.
Certainly you could build a similar service on top of, say, RDS, but without the features listed above, I think it would take a lot more work and not come out as well.
Hope that helps.
Re: Heroku Postgres
#44If 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
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.
Re: Heroku Postgres
#45This is really awesome! A couple questions though:
* What do I do if I need to tune/configure Postgres for my workload.
* How is the performance of transferring all of the queries and responses across the internet?
Keep in mind I've never used postgres before so these may be moot points.
Re: Heroku Postgres
#46"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 ?
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."
Re: Heroku Postgres
#47Any chance of PL/python or similar? I guess I'm probably one of like three users of PL/python, especially since it's untrusted. Worth a check, though!
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 cool: http://code.google.com/p/plv8js/wiki/PLV8
Re: Heroku Postgres
#48This is really awesome! A couple questions though: * What do I do if I need to tune/configure Postgres for my workload. * How is the performance of transferring all of the queries and responses across the internet? Keep in mind I've never used postgres before so these may be moot points.
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 overhead is typically <1ms.
Re: Heroku Postgres
#49Is this still using the EBS RAID that you guys mentioned in a blog post a while ago? If so, how do you avoid any slow I/O requests (which plague EBS) stalling all I/O to the volume?
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 several kinds of related problems and in the most dire of straights can perform a hardware migration to a quieter node which generally clears issues up.
Re: Heroku Postgres
#50I 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.
Ah, good to know. I haven't got around to creating a Cedar-based app yet