public inbox for [email protected]
help / color / mirror / Atom feedFrom: Holger Jakobs <[email protected]>
To: [email protected]
Subject: Re: Question about permissions in the Schema
Date: Tue, 3 Jun 2025 14:02:06 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <PAXP194MB1230AFF50B791AD42BAF6EFE8C6DA@PAXP194MB1230.EURP194.PROD.OUTLOOK.COM>
References: <PAXP194MB1230AFF50B791AD42BAF6EFE8C6DA@PAXP194MB1230.EURP194.PROD.OUTLOOK.COM>
Am 03.06.25 um 13:44 schrieb Sabyasachi Mukherjee:
> Hello,
> I have a database with 5 different schemas. Each schema has the same
> set of tables, but the data is different.
> I have created one user to access the data in the tables from one
> schema only.
> The user can access the data from the target schema. For all other
> schemas it get a permission error except one.
> I have specifically run the Revoke command for the schema but still
> the user can access the data from that schema. I have run the command
> in PGAdmin. Also DBBeaver does not any permission for the objects in
> the leaking schema for the user.
> What could be wrong and how should I fix it.
> I am running PG 17 on Linux.
>
> Thanks & Regards
>
> Sabyasachi Mukherjee
Dear S. M.,
Even if a role (user) personally doesn't have any permissions to access
a schema, memerships in other roles (groups) may allow access.
Check memberships and never, ever grant permissions to individual user
roles, but only to non-login (group) roles. This minimises the number of
grants and enhances clarity of permissions.
Kind Regards,
Holgger
--
Holger Jakobs, Bergisch Gladbach
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Question about permissions in the Schema
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox