Dear group,
I have the issue that I have a postgres database on which I revoked from public to see the public schema and catalog. My user is only suppose to query very specific functions and database views, but shall not be allowed to browse e.g. the database schema or execute other functions.
When I use psql then everything works as expected. The user can't inspect the query or get any information from the database schema, but that account is able to execute the functions and views to which the SELECT was granted.
When I try to use this account with PGAdmin4, then even the connection to the database is failing. It seems that it is mandatory for PGAdmin4 to be able to browse the schema. Can this be disabled? Or at least optional? Maybe there can be a fallback to simply not populate the object tree? PGAdmin4 should allow to connect to the database, and if the catalog can't be queried, simply not populate the database object tree. Then the user can use PGAdmin4 e.g. to open a query window on the database and run the queries allowed for the user.
Is this issue already known? Or even already working? What would I have to configure in the preferences to get my desired behavior?
Thanks, Michael
PGAdmin4 ( v 3.1 on Mac )