| From: | Mark Phillips <mphillips(at)mophilly(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Row level security policy |
| Date: | 2024-11-14 02:13:24 |
| Message-ID: | 3D0A30B0-0A39-4F71-9449-415196B631DE@mophilly.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Thank you. I will revisit my test cases to be sure I have the use cases covered.
- Mark, out and about.
On Nov 13, 2024, at 5:36 PM, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Phillips | 2024-11-14 05:05:34 | Re: Row level security policy |
| Previous Message | David G. Johnston | 2024-11-14 01:36:27 | Re: Row level security policy |