Re: Row level security policy

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Mark Phillips <mphillips(at)mophilly(dot)com>
Cc: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Row level security policy
Date: 2024-11-14 01:36:27
Message-ID: CAKFQuwbJC2iLVj0-RCGhZ+DWPf3e8_n3krBpY6K5EuUyNghcsw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wednesday, November 13, 2024, Mark Phillips <mphillips(at)mophilly(dot)com>
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?
>

It isn’t necessary but most conventional use cases would involve
establishing policies for writing as well as reading. But it is use case
dependent.

David J.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Mark Phillips 2024-11-14 02:13:24 Re: Row level security policy
Previous Message Mark Phillips 2024-11-14 01:33:47 Row level security policy