The email sent to existing customers mentions price drops for certain plans (text below). With the few plans I glanced at for 2.0, it doesn't look so much like a price drop as it does a storage capacity and max connections drop.<p>Production plans used to allow 1TB of storage and 500 connections. Now the smallest production plan has dropped to 64GB of storage and 60 connections.<p>I know Heroku is trying to run a business, and that computing resources do cost money -- but that copy seems a bit misleading to me.<p>Customer email blast:<p>"""
As someone who is already using a Heroku Postgres production database we’re excited to ensure you’re the first to know about our new release, Heroku Postgres 2.0. This new release continues to build on many of the great features you may already take advantage of as well as a price drop across certain plans. This new release highlights:<p>Built-in alerts around what you should do for your database, bringing a new level of operational expertise built right into the product.
The ability to rollback your database to a specific point in time, similar to how you can rollback bad deploys on Heroku
New tiers, with our premium and enterprise tiers including high availability with automatic failover
You can read more details about the features included within this release on our blog post.<p>You will be able to continue using your existing plans. While they will not appear in the addons:list you will be able to visit the legacy pricing page and they will continue working. We will notify you before any changes do occur to existing plans.<p>Cheers,
The Heroku Postgres team
"""
I just had a look at the updated pricing.<p>If my memory serves correctly, the same limits for storage and # of connections were in place before for the non-dev databases (starting with 50$). I don't really care for the connections, but a 64 GB storage limit can quickly become a problem for some apps, while 400MB of RAM is perfectly fine to serve the hot data...<p>Edit: To put this into perspective: If an app would generate 400MB of data per day (the last 24 hours would fit into the cache completely!), the app would run out of storage after 160 days...