| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Joseph Kennedy <joseph(dot)kennedy(dot)486(at)gmail(dot)com> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Giovanni Biscontini <biscontini(dot)g(at)es2000(dot)it>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: PostgreSQL |
| Date: | 2023-04-03 09:45:00 |
| Message-ID: | 5aec0a43c2e3d4c7be2d010b0e0684253cdb1f1e.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sun, 2023-04-02 at 23:21 +0200, Joseph Kennedy wrote:
> I have one more question on this topic regarding Row Level Security.
>
> I would like to hide some rows for users who should have full rights to database
> eg. create Index, drop table, create tabel etc. but e.g. create index can be
> done by owner or superusers but they are bypassed by Row Level Security.
>
> Is possible to use RLS for users who should have full rights to database ?
If "full rights" implies dropping tables, the user must either be the owner
of these tables or a superuser. You cannot use Row Level Security with a
superuser. You can use ALTER TABLE ... FORCE ROW LEVEL SECURITY, so that
Row Level Security applies to the table owner as well, but you cannot keep
the owner from disabling that setting.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2023-04-03 09:53:40 | Re: Question on creating keys on partitioned tables |
| Previous Message | Arnaud Lesauvage | 2023-04-03 07:12:09 | RE: Cannot terminate backend |