MIME-Version: 1.0
From: Sanjay Minni <sanjay.minni@gmail.com>
Date: Thu, 12 Sep 2024 18:49:07 +0530
Message-ID: <CAMpxBomfErwT=ETjdzrVM9Kys8E3xZ2Lge9kY_SahyOCtX8dCQ@mail.gmail.com>
Subject: RLS and Table Inheritance
To: "pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="0000000000001dfa2c0621ebf5d6"
Archived-At: <https://www.postgresql.org/message-id/CAMpxBomfErwT%3DETjdzrVM9Kys8E3xZ2Lge9kY_SahyOCtX8dCQ%40mail.gmail.com>
Precedence: bulk

--0000000000001dfa2c0621ebf5d6
Content-Type: text/plain; charset="UTF-8"

Hi,

Do RLS policies defined at the parent, work on the child (in Table
inheritance).
At the parent I have a column 'site_id' with an RLS policy that only rows
with site_id = current_setting(curr_site_id) would be accessible.
However the policy defined at the parent does not work for me in inherited
tables. Is it intended that way ?
Is there a solution to reflect the RLS policy along the line of
inheritance, else i have to redefine the RLS policy at each inherited table
(a significant maintenance effort).

In another post I see conflicting views on this
https://www.postgresql.org/message-id/d094a87d-9d63-46c9-8c27-631f881b80fb@supportex.net
.
While the original post seemed to get a prototype working,  the response
says that RLS policy will not be inherited and needs to be reimplemented at
each table.

thanks
Sanjay

--0000000000001dfa2c0621ebf5d6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:verdana,=
sans-serif">Hi,</div><div class=3D"gmail_default" style=3D"font-family:verd=
ana,sans-serif"><br></div><div class=3D"gmail_default" style=3D"font-family=
:verdana,sans-serif">Do RLS policies defined at the parent, work on the chi=
ld (in Table inheritance).</div><div class=3D"gmail_default" style=3D"font-=
family:verdana,sans-serif">At the parent I have a column &#39;site_id&#39; =
with an RLS policy that only rows with site_id =3D current_setting(curr_sit=
e_id) would be accessible.=C2=A0</div><div class=3D"gmail_default" style=3D=
"font-family:verdana,sans-serif">However the policy defined at the parent d=
oes not work for me in inherited tables. Is it intended that way ?</div><di=
v class=3D"gmail_default" style=3D"font-family:verdana,sans-serif">Is there=
 a solution to reflect the RLS policy along the line of inheritance, else i=
 have to redefine the RLS policy at each inherited table (a significant mai=
ntenance effort).</div><div class=3D"gmail_default" style=3D"font-family:ve=
rdana,sans-serif"><br></div><div class=3D"gmail_default" style=3D"font-fami=
ly:verdana,sans-serif">In another post I see conflicting views on this <a h=
ref=3D"https://www.postgresql.org/message-id/d094a87d-9d63-46c9-8c27-631f88=
1b80fb@supportex.net">https://www.postgresql.org/message-id/d094a87d-9d63-4=
6c9-8c27-631f881b80fb@supportex.net</a>.</div><div class=3D"gmail_default" =
style=3D"font-family:verdana,sans-serif">While the original post seemed to =
get a prototype working,=C2=A0 the response says that RLS policy will not b=
e inherited and needs to be reimplemented at each table.</div><div class=3D=
"gmail_default" style=3D"font-family:verdana,sans-serif"><br></div><div cla=
ss=3D"gmail_default" style=3D"font-family:verdana,sans-serif">thanks=C2=A0<=
/div><div class=3D"gmail_default" style=3D"font-family:verdana,sans-serif">=
Sanjay</div><div class=3D"gmail_default" style=3D"font-family:verdana,sans-=
serif"><br></div><div class=3D"gmail_default" style=3D"font-family:verdana,=
sans-serif"><br></div></div>

--0000000000001dfa2c0621ebf5d6--