We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Users/databases on pgtle.clientauth_users_to_skip and pgtle.clientauth_databases_to_skip do not take effect if their names are mixed case.
pgtle.clientauth_users_to_skip
pgtle.clientauth_databases_to_skip
CREATE ROLE "MixedCase";
ALTER SYSTEM SET pgtle.clientauth_users_to_skip = 'MixedCase'; SELECT pg_reload_conf()
MixedCase
Clientauth function should be skipped for MixedCase.
Clientauth function is executed.
This behaviour can be reproduced similarly for mixed-case database names.
The text was updated successfully, but these errors were encountered:
Merged
Sorry, something went wrong.
No branches or pull requests
Description
Users/databases on
pgtle.clientauth_users_to_skip
andpgtle.clientauth_databases_to_skip
do not take effect if their names are mixed case.Steps to reproduce
CREATE ROLE "MixedCase";
pgtle.clientauth_users_to_skip
and reload config:ALTER SYSTEM SET pgtle.clientauth_users_to_skip = 'MixedCase'; SELECT pg_reload_conf()
MixedCase
Expected outcome
Clientauth function should be skipped for
MixedCase
.Actual outcome
Clientauth function is executed.
This behaviour can be reproduced similarly for mixed-case database names.
The text was updated successfully, but these errors were encountered: