Re: Clarification on RLS policy

From: Vydehi Ganti <rayudugs(at)gmail(dot)com>
To: Dominique Devienne <ddevienne(at)gmail(dot)com>
Cc: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Clarification on RLS policy
Date: 2025-04-29 08:05:59
Message-ID: CAMH-PzXKwDgS3dk8VDJ8aUp859wf0-vpTevxGFaxZZzCgGzbkQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi,

Checking the documents .
Post fetching Boolean can we have a trigger or function which can build up
the where filter clause?
Or can i have a case statement in the Using which can return such
statements?

On Fri, Apr 25, 2025 at 7:02 PM Dominique Devienne <ddevienne(at)gmail(dot)com>
wrote:

> On Fri, Apr 25, 2025 at 3:29 PM Vydehi Ganti <rayudugs(at)gmail(dot)com> wrote:
> > Can i know if there is any scenario or ref document for the design you
> suggested above?
>
> Some docs:
> https://www.postgresql.org/docs/current/ddl-rowsecurity.html
> https://satoricyber.com/postgres-security/postgres-row-level-security/
>
> Your Oracle function converted to PostgreSQL, FWIW. Use at your own risk.
> https://chatgpt.com/share/680b8e36-b4ac-800e-9e0e-2601aecd2aee
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Duygu Hasan 2025-04-29 10:43:49 Pg client certificate auth
Previous Message Laurenz Albe 2025-04-29 06:36:14 Re: Upsert error "column reference is ambiguous"