From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Joseph Kennedy <joseph.kennedy.486@gmail.com>
To: Giovanni Biscontini <biscontini.g@es2000.it>
Cc: pgsql-general@postgresql.org
Subject: Re: PostgreSQL
Date: Tue, 07 Feb 2023 15:34:23 +0100
Message-ID: <dabd6f968361f363f2ecb93a7be2bc27ddd68908.camel@cybertec.at> (raw)
In-Reply-To: <81AB3CB7-93E6-4811-9097-5C535FA84BFC@gmail.com>
References: <CAOM+UfXknNh+9nTPbSWrvncxcBrU9tFRL4aLaBzgQdm6sJrPnw@mail.gmail.com>
<81AB3CB7-93E6-4811-9097-5C535FA84BFC@gmail.com>
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
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: laurenz.albe@cybertec.at, joseph.kennedy.486@gmail.com, biscontini.g@es2000.it
Subject: Re: PostgreSQL
In-Reply-To: <dabd6f968361f363f2ecb93a7be2bc27ddd68908.camel@cybertec.at>
References: <CAOM+UfXknNh+9nTPbSWrvncxcBrU9tFRL4aLaBzgQdm6sJrPnw@mail.gmail.com> <81AB3CB7-93E6-4811-9097-5C535FA84BFC@gmail.com> <dabd6f968361f363f2ecb93a7be2bc27ddd68908.camel@cybertec.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox