Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Note permissions schema configuration Heroku caveats #451

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jeffbax
Copy link

@jeffbax jeffbax commented Apr 10, 2023

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)

I recently attempted an upgrade of Postgres on Heroku, and had it 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 was reminded of a few steps here that did not seem to apply to database instances there that I figured were worth calling out for others deploying there.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant