Message-ID: <e02436cddbd2f628062f12365c9868b5ea124737.camel@cybertec.at>
Subject: Re: Row level security policy
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Mark Phillips <mphillips@mophilly.com>, 
	pgsql-general@lists.postgresql.org
Date: Thu, 14 Nov 2024 10:57:38 +0100
In-Reply-To: <3BA7883C-2247-4687-A764-5777EB8755EF@mophilly.com>
References: <3BA7883C-2247-4687-A764-5777EB8755EF@mophilly.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.52.4 (3.52.4-2.fc40) 
MIME-Version: 1.0
Archived-At: <https://www.postgresql.org/message-id/e02436cddbd2f628062f12365c9868b5ea124737.camel%40cybertec.at>
Precedence: bulk

On Wed, 2024-11-13 at 17:33 -0800, Mark Phillips wrote:
> Given a database table with one policy statement FOR SELECT applied, it i=
s necessary
> to apply additional policy statements for insert, update, and delete oper=
ations?
>=20
> My testing indicates that this is case but I haven=E2=80=99t found an exp=
lanation of this
> requirement in the documentation.

https://www.postgresql.org/docs/current/ddl-rowsecurity.html says:

  When row security is enabled on a table (with ALTER TABLE ... ENABLE ROW =
LEVEL SECURITY),
  all normal access to the table for selecting rows or modifying rows must =
be allowed by
  a row security policy.

So if you only have a policy for SELECT, that's all you are allowed to do.

Yours,
Laurenz Albe