need GIS And confused by "one database only". Does that mean CREATE DATABASE databases? If so why?
Ya me too, no mention of PostGIS.
PostGIS is currently in a pilot phase. If you're serious, please contact me as described elsewhere on this thread.
Heroku Postgres
71–78 of 78 posts
Re: Heroku Postgres
#72Just 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.
They are built on different EC2 instances.
Ronin = Small Instance: 1.7 GB of memory, 1 EC2 Compute Unit (1 virtual core with 1 EC2 Compute Unit), 160 GB of local instance storage, 32-bit platform. ~$60/month spot.
Fugu = High-CPU Medium Instance: 1.7 GB of memory, 5 EC2 Compute Units (2 virtual cores with 2.5 EC2 Compute Units each), 350 GB of local instance storage, 32-bit platform. ~$120/month spot.
Ikea = Large Instance: 7.5 GB of memory, 4 EC2 Compute Units (2 virtual cores with 2 EC2 Compute Units each), 850 GB of local instance storage, 64-bit platform. ~$240 / month spot.
Zilla = High-Memory Extra Large Instance: 17.1 GB memory, 6.5 ECU (2 virtual cores with 3.25 EC2 Compute Units each), 420 GB of local instance storage, 64-bit platform. ~$360/month spot.
Baku = High-Memory Double Extra Large Instance: 34.2 GB of memory, 13 EC2 Compute Units (4 virtual cores with 3.25 EC2 Compute Units each), 850 GB of local instance storage, 64-bit platform. ~$720/month spot.
Mecha = High-Memory Quadruple Extra Large Instance: 68.4 GB of memory, 26 EC2 Compute Units (8 virtual cores with 3.25 EC2 Compute Units each), 1690 GB of local instance storage, 64-bit platform. ~$1440/month spot.
I think Heroku will pay less than the spot price for the raw server, but fork out bandwidth, storage, EBS IO, backups and so on. Amazon sells its basic servers cheap, but virtually nothing is included.
It looks like their margins go up at Zilla, but maybe the high-RAM instances need more bandwidth and backups.
Re: Heroku Postgres
#73Earlier quoted context omitted.
I'm a real fan of PostGIS and like ltree and hstore a lot. Heroku isn't quite right for my needs at this time, but I would definitely consider it if I had a use case that needed an extremely fast public facing postgres installation. I am curious as to whether you do pro-rated pricing?
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.
That is interesting, there are times when I want to use PG as an ETL tool and take a midsized ( < 2tb data ) set and load it up and slice and dice it and produce some output for other programs and then have it go away. So, I'll keep you guys in mind.
Re: Heroku Postgres
#74need GIS And confused by "one database only". Does that mean CREATE DATABASE databases? If so why?
Ya me too, no mention of PostGIS.
Hi co-founder of SpacialDB here. Cloud hosted PostGIS is already available as a Heroku plugin, stand-alone and an easy to use API. Check out http://devcenter.spacialdb.com/ for documentation and you can sign up via the Heroku addons page or http://beta.spacialdb.com/
Re: Heroku Postgres
#75If 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.
I have contributed a little bit to Sequel Pro, and I'm a bit familiar with the codebase. Adding support for PostgreSQL is not trivial, a lot of MySQL is hardcoded into the user interface. There have always been many requests for PostgreSQL compatibility, but it would require A LOT of refactoring.
(Disclaimer: I haven't been involved much with SP for almost a year now, so possibly there has been progress in that time)
Re: Heroku Postgres
#76Re: Heroku Postgres
#77Earlier quoted context omitted.
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 ex…
I'm a real fan of PostGIS and like ltree and hstore a lot. Heroku isn't quite right for my needs at this time, but I would definitely consider it if I had a use case that needed an extremely fast public facing postgres installation. I am curious as to whether you do pro-rated pricing?
@Olefoo you can get PostGIS on Heroku via SpacialDB. SpacialDB is cloud hosted PostGIS and a convenient RESTful API. We have a heroku addon too currently in private beta. Check out our devcenter here: http://devcenter.spacialdb.com/ and let us know if you would like a beta invite.
Re: Heroku Postgres
#78Earlier quoted context omitted.
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.
I have contributed a little bit to Sequel Pro, and I'm a bit familiar with the codebase. Adding support for PostgreSQL is not trivial, a lot of MySQL is hardcoded into the user interface. There have always been many requests for PostgreSQL compatibility, but it would require A LOT of refactoring. (Disclaimer: I haven't been involved much with SP for almost a year now, so possibly there has been progress in that time)
As one of the current Sequel Pro developers I can backup jabkobob on this one, it's not an easy task. It's not that we're ignoring the requests we get to add support for PostgreSQL or any other database system for that matter, it's simply a matter of time, of which most of the core devs don't have just now. We have a lot of plans around this area (as well as others) for the app, but it's going to take time.
Thanks for everyone's support.