Re: RLS makes COPY TO process child tables - Mailing list pgsql-hackers

From Tom Lane
Subject Re: RLS makes COPY TO process child tables
Date
Msg-id 825494.1678466042@sss.pgh.pa.us
Whole thread Raw
In response to Re: RLS makes COPY TO process child tables  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
Stephen Frost <sfrost@snowman.net> writes:
>> Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> Yugo NAGATA <nagata@sraoss.co.jp> writes:
>>>> I think this is a bug because the current behaviour is different from
>>>> the documentation. 

>>> I agree, it shouldn't do that.

> Yeah, I agree based on what the COPY table TO docs say should be
> happening.

Yeah, the documentation is quite clear that child data is not included.

> I'm not sure if this makes good sense to back-patch.

I think we have to.  The alternative is to back-patch some very confusing
documentation changes saying "never mind all that if RLS is on".

            regards, tom lane



pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: pgsql: Use ICU by default at initdb time.
Next
From: Chris Travers
Date:
Subject: Re: POC: Lock updated tuples in tuple_update() and tuple_delete()