New issue
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
psql should assume role set in server properties #5807
Comments
I report the same bug in release 6.18 and it is now fixed in release 6.20. |
Still not working for me in v6.20. |
Delete your current server and create it again. |
@pr2git The roles and username were correctly saved. There was code bug which was taking role as username. |
So do you explain that existing servers were working but newly added were not? |
…in server properties. pgadmin-org#5807 2. Corrected title in query tool connection link.
…in server properties. pgadmin-org#5807 2. Corrected title in query tool connection link.
…in server properties. pgadmin-org#5807 2. Corrected title in query tool connection link.
…in server properties. #5807 2. Corrected title in query tool connection link.
Tested and verified on snapshot build: https://www.postgresql.org/ftp/pgadmin/pgadmin4/snapshots/2023-11-13/ |
Describe the bug
psql is not taking the role set in the server properties.
When a role is set in server properties, the role is assumed when a new connection is created. Currently, this is happening for query tool but not for psql.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
SELECT current_user, session_user should return otherrole, postgres.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: