Message-ID: <88804c921b425d37a3072b5698b558a763d80d63.camel@cybertec.at>
Subject: Re: Clarification on RLS policy
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Vydehi Ganti <rayudugs@gmail.com>, pgsql-general@lists.postgresql.org
Date: Fri, 25 Apr 2025 14:43:22 +0200
In-Reply-To: <CAMH-PzUPN7JcLXJx-aJzGnJD2T-aSMo8gaMFkzO_x26urpMqSA@mail.gmail.com>
References: 
	<CAMH-PzUPN7JcLXJx-aJzGnJD2T-aSMo8gaMFkzO_x26urpMqSA@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.54.3 (3.54.3-1.fc41) 
MIME-Version: 1.0
Archived-At: <https://www.postgresql.org/message-id/88804c921b425d37a3072b5698b558a763d80d63.camel%40cybertec.at>
Precedence: bulk

On Fri, 2025-04-25 at 12:38 +0530, Vydehi Ganti wrote:
> We are presently using Postgresql:PostgreSQL 15.12 on x86_64-pc-linux-gnu=
, compiled by gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-23), 64-bit
> I have a scenario where
> 1.I need to enforce RLS policy on a table for Select by calling a Functio=
n
> 2.The function would return a character varying string which should be ap=
pended
>   to the select as a filter.
> Ex: Select * from employee would=C2=A0be appended=C2=A0with where 1=3D1;
> 3.When we try to implement it says the below error.
>   ERROR: invalid input syntax for type boolean: "1=3D1" CONTEXT: PL/pgSQL=
 function function name(name,name) while casting return value to function's=
 return type
> 4.It works fine on Oracle. Can you please suggest how to fix this issue?

You cannot add whole WHERE conditions to a query dynamically.
The only way to fix that is to solve the problem differently.
Since you didn't tell us details, we cannot tell you how.

Yours,
Laurenz Albe