| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Joseph Kennedy <joseph(dot)kennedy(dot)486(at)gmail(dot)com>, Giovanni Biscontini <biscontini(dot)g(at)es2000(dot)it> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: PostgreSQL |
| Date: | 2023-02-07 14:34:23 |
| Message-ID: | dabd6f968361f363f2ecb93a7be2bc27ddd68908.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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 | Laurenz Albe | 2023-02-07 14:37:38 | Re: ERROR: deadlock detected |
| Previous Message | Philip Semanchuk | 2023-02-07 14:09:12 | Re: ALTER COLUMN to change GENERATED ALWAYS AS expression? |