2 ms·
Product manager of Heroku Postgres here, we did indeed lower those limits, but less for the cost and more that we saw many users hitting issues in going beyond
by craigkerstiens 13y ago
Product manager of Heroku Postgres here, we did indeed lower those limits, but less for the cost and more that we saw many users hitting issues in going beyond that. Our limits exist primarily to prevent people from shooting themselves in the foot and bringing their databases down. Would be happy to hear if you're above one of those limits today and not experiencing problems - postgres@heroku.com
- erikcw 13y agoI have a production app that generates about 500MB of data per day. A small amount of that data needs to be kept hot in cache -- but the rest is accessed infrequently by comparison (but still in a manner that is aided by SQL). No problems at all -- system runs smooth as silk. The problem is the application was developed based on the specs advertised (as I'm sure countless others also were). Now, the smallest database package with the same storage and connection resources is the "Standard Baku" at $2,000/month. These resources used to be available starting at $50/month. Ouch!! And even then, it is still only the "Standard" feature set -- so none of the new whiz-bang Heroku 2.0 features.