From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | Mark Phillips <mphillips(at)mophilly(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Row level security policy |
Date: | 2024-11-14 09:57:38 |
Message-ID: | e02436cddbd2f628062f12365c9868b5ea124737.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, 2024-11-13 at 17:33 -0800, Mark Phillips wrote:
> Given a database table with one policy statement FOR SELECT applied, it is necessary
> to apply additional policy statements for insert, update, and delete operations?
>
> My testing indicates that this is case but I haven’t found an explanation 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
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Phillips | 2024-11-14 12:04:00 | Re: Row level security policy |
Previous Message | jayakumar s | 2024-11-14 09:14:09 | Re: DB wal file disabled --_Query |