Honor --no-role-passwords when emitting PASSWORD - #69
Open
Smyatkin-Maxim wants to merge 2 commits into
Open
Conversation
Emit PASSWORD in CREATE ROLE, and only emit the GPDB profile / pg_authid account-status UPDATE block when server_version >= 140000 and a profile exists. The old code always emitted that block (invalid against a GPDB6 source / Cloudberry target) and never dumped the password. Co-authored-by: Cursor <cursoragent@cursor.com>
Otherwise we gonna get masks instead of passwords
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Otherwise we gonna get masks instead of passwords