| From: | Joseph Kennedy <joseph(dot)kennedy(dot)486(at)gmail(dot)com> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | Giovanni Biscontini <biscontini(dot)g(at)es2000(dot)it>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: PostgreSQL |
| Date: | 2023-02-07 14:46:39 |
| Message-ID: | 8C7CE513-7187-428E-81C2-508C85812B54@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Thank you Laurenz, I just wanted to make sure.
Do you know any alternative solution to RLS ?
> Wiadomość napisana przez Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> w dniu 07.02.2023, o godz. 15:34:
>
> On Tue, 2023-02-07 at 12:36 +0100, Joseph Kennedy wrote:
>> RLS policy it only affects to command as SELECT, INSERT, UPDATE, DELETE or
>> can affects to operations on whole database, table like vacuum or reindex etc ?
>
> No, that wouldn't make any sense. Row Level Security determines who
> is allowed to see or create which data. Jobs like removing dead tuples
> or rebuilding an index have nothing to do with that.
>
> Besides, anything that requires the table owner or a superuser cannot
> be reasonably controlled with row level security, because both the
> table owner and a superuser are exempt from RLS anyway.
>
> Yours,
> Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2023-02-07 14:47:17 | Re: Sequence vs UUID |
| Previous Message | Laurenz Albe | 2023-02-07 14:37:38 | Re: ERROR: deadlock detected |