5 ms·
Heroku announces support for 17 new Postgres extensions
- bryanlarsen 14y agoI was hoping for postgis when I saw the title . Hopefully that's coming soon.
- craigkerstiens 14y agoWe do currently have a public beta for PostGIS (https://devcenter.heroku.com/articles/is-postgis-available https://devcenter.heroku.com/articles/is-postgis-available) though it is only available on certain plans and is not yet GA like the other extensions.
- deleted 14y ago[deleted]
- shykes 14y agoHere's a tutorial for postgres + postgis on dotCloud: http://docs.dotcloud.com/services/postgresql/ http://docs.dotcloud.com/services/postgresql/
- don_draper 14y agoltree looks awesome. I didn't know it was in there.
- willlll 14y agoMy favorite is fuzzystrmatch. It gives you the soundex function which lets you match things that kinda-sorta-sound-the-same. Example: https://postgres.heroku.com/dataclips/inpkhuzaczuwoppmudblesrjzxle https://postgres.heroku.com/dataclips/inpkhuzaczuwoppmudbles...
- exogen 14y agoSince the dblink extension is available even on the free dev plan, is anything stopping you from creating a bunch of dev databases and linking them together to overcome size restrictions? Sounds kinda fun, although there will of course be concerns over performance, integrity constraints, etc.
- the1 14y agodo you have 20 credit cards for 100MB of free database?
- ceejayoz 14y agoPayPal lets you generate one-time use credit card numbers, don't they?
- deleted 14y ago[deleted]
- k33l0r 14y agoOnly in the US.
- exogen 14y agoYou can add as many free dev databases as you want with a single account AFAIK. You aren't limited to one per app, account, or plan.
- andypants 14y agoNo, heroku has a postgres service where you can create as many free dev databases as you want. These have no size restriction, just a 10,000 row limit and 0MB cache, as well as some other feature limitations.
- pearkes 14y agoI recall hearing folks at Heroku talk about this before - basically the message was yes, there are many ways to abuse the free service but they rarely have people _actually_ doing it. Kind of interesting, as it would be pretty trivial to use many single dynos (with shared caching, db) in one account for one application.
- pygy_ 14y agoAccording to the Postgres documentation, CHKPass is implemented on top of the crypt() unix function. More details would be welcome... What hashing function are you using at Heroku? Short of bcrypt, all it gives is a false sense of security. As is, it sounds more dangerous than useful.
- kingkilr 14y agoThere are plenty of reasonable options besides bcrypt, including PBKDF2 and scrypt.
- fdr 14y agoTo that mind, the post has been amended to drop support for that one extension. Unless you have a great use case, it seems like the consensus is "do not use chkpass". pgcrypto should have everything one needs and probably a few more things.
- plasma 14y agoAny performance benchmarks of pgsql on heroku?
- exogen 14y agoI've looked and haven't found any. But it should be relatively easy and cheap to run your own specific throughput tests, since databases are metered by the second just like dynos. I just confirmed with Heroku support that you could (for example) spin up the $6,400 database plan, run the tests for (say) half an hour, then destroy it. You'd only be charged about $5 in that case.
- pbreit 14y agoIs Postgres gaining momentum such that it might displace MySQL as the go-to DB?
- jamescun 14y agoI doubt it. While PostgreSQL offers a number of technological advantages over MySQL, MySQL has a lower barrier to entry and easier to understand concepts than PostgreSQL as well as being a major part of the LAMP stack, which is still the most common entry point of web development. Rather than viewing one database solution as the dominant, what we are likely to see is the diversification of database technologies with the likes of NoSQL solutions coming to prominence in stacks.
- gbog 14y ago> MySQL has a lower barrier to entry and easier to understand concepts than PostgreSQL This affirmation need some explanation. In my view, once SQL is understood, both are similar. PostgreSQL might even be simpler, as it has no concept of "engines".
- emperorcezar 14y agoI think it will depend on your community. In the Django community, postgres has always been around and is gaining a ton of momentum. PHP world, probably always a MySQL offshoot of some sort.
- jacques_chester 14y agoFor new apps -- perhaps. But existing apps are riddled with MySQLisms.
- fomojola 14y agoIts a small point, but I feel that MySQL administration via the console is easier to get into (for example, having SHOW CREATE TABLE to dump table creation SQL is operationally simpler than having to exit out of the console, then run pg_dump <db> --schema-only <tablename> and then start the console back up). MySQL does a lot of simplifications in that vein that I think will prevent displacement for some time to come.