Horton

Re: RLS makes COPY TO process child tables

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Stephen Frost <sfrost@snowman.net>
Cc: Yugo NAGATA <nagata@sraoss.co.jp>, Antonin Houska <ah@cybertec.at>, pgsql-hackers@postgresql.org
Date: 2023-03-10T16:34:02Z
Lists: 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

Commits

  1. Ensure COPY TO on an RLS-enabled table copies no more than it should.