Monkey Patch Postgres to fix Panic string issue. #182
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This blew up the app with error around ‘panic’ as a status
Found via https://stackoverflow.com/questions/58763542/pginvalidparametervalue-error-invalid-value-for-parameter-client-min-messag Heroku just upgraded Postgres to something … which I can’t tell which version or why this started failing.
|
Hey, I pulled this PR to test the fix, but found that the error remained upon running the command Did you run a command before the one above, for the app to 'apply' the fix? |
|
Probably have to run |
|
Sorry, that didn't work for me; running For now, I have used this workaround. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Overview
Heroku upgraded our Postgres version today via regular maintenance (12-10-2020) and it brought down with a message
PG::InvalidParameterValue: ERROR: invalid value for parameter “client_min_messages”: “panic”Found a way to monkey patch and get the app back up via:
https://stackoverflow.com/questions/58763542/pginvalidparametervalue-error-invalid-value-for-parameter-client-min-messag
I think a better option would to re-provision to postgres 9.6 specifically. I couldn't check the version this AM, but best guess is that we are on 10 or 11 version that dropped the support for 'panic'. I don't have a ton of knowledge about this as of now