Note permissions schema configuration Heroku caveats #451
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I recently attempted an upgrade of Postgres on Heroku, and had the process fail because of this schema extension.
The
pg:upgrade
command was in no hurry to tell me why, so we incurred some longer downtime than was necessary. Then when re-adding this schema I was reminded of a few steps here that did not seem to apply to database instances there, which I figured were worth calling out for others deploying on Heroku.It also seems that when using https://elements.heroku.com/buttons/pghero/pghero, while still functioning, it installs software that is a bit out of date. Probably not pressing, and I might be the only one using this these days, but given it works so well otherwise it might be cool to check. (I don't think there is a public repo for me to try to update for that)