Remove db_user_namespace parameter for PostgreSQL 17 compatibility
#2571
Conversation
8000
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
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.
Description:
In PostgreSQL 17, the
db_user_namespaceparameter has been removed as it was a rarely used feature that simulated per-database users. This causes an error when the parameter is included in thepostgresql.confconfiguration file:This PR removes the
db_user_namespaceparameter from the Ansible collection to ensure compatibility with PostgreSQL 17.Changes:
db_user_namespaceparameter from the PostgreSQL configuration template.References:
Testing:
db_user_namespaceparameter.