If a review app requires loading in data with more than 10,000 rows, Heroku will send an angry email to whoever "deployed" that review app saying that disruption of the database is imminent because of exceeded row limits. These emails can be safely ignored, but they're annoying.
The only way I can see to block these emails would be to upgrade review apps that require more than 10,000 rows to larger Heroku Postgres plans, but unfortunately there doesn't seem to be a way to do this in an automated fashion because Heroku defaults to the cheapest plan for review apps.
We should provide some guidance in the Heroku docs on how to deal with these emails. I think the potential ways of dealing with these emails are:
Work to define a "sample" set of data that's smaller than 10,000 rows
Documentation request
If a review app requires loading in data with more than 10,000 rows, Heroku will send an angry email to whoever "deployed" that review app saying that disruption of the database is imminent because of exceeded row limits. These emails can be safely ignored, but they're annoying.
The only way I can see to block these emails would be to upgrade review apps that require more than 10,000 rows to larger Heroku Postgres plans, but unfortunately there doesn't seem to be a way to do this in an automated fashion because Heroku defaults to the cheapest plan for review apps.
We should provide some guidance in the Heroku docs on how to deal with these emails. I think the potential ways of dealing with these emails are: