Fix incorrect value password_encryption for >10 #396
Closed
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
In >=10 the `password_encryption` option is no longer a boolean, but rather should explicitly specify the password encryption algorithm. If you migrated to SCRAM-SHA256 the current seting will revert it back to MD5. This fix will set the configured value for >=10.
|
Is this or #368 the preferred way? |
|
@rbjorklin #368 is simpler so I'd just go for that PR. |
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.
In >=10 the
password_encryptionoption is no longer a boolean, butrather should explicitly specify the password encryption algorithm.
If you migrated to SCRAM-SHA256 the current seting will revert it back
to MD5. This fix will set the configured value for >=10.