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
Subject: Re: RLS makes COPY TO process child tables
In-reply-to: <Y+L0jZJkHvgdOZRA@tamriel.snowman.net>
References: <3472.1675251957@antos>
 <20230202011525.c7c05900bcf791f868d72a51@sraoss.co.jp>
 <1379089.1675270043@sss.pgh.pa.us>
 <20230202160031.defd38f35433c7677b48a8ec@sraoss.co.jp>
 <Y+L0jZJkHvgdOZRA@tamriel.snowman.net>
Comments: In-reply-to Stephen Frost <sfrost@snowman.net>
	message dated "Tue, 07 Feb 2023 20:02:05 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <978237.1678474675.1@sss.pgh.pa.us>
Date: Fri, 10 Mar 2023 13:57:55 -0500
Message-ID: <978238.1678474675@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/978238.1678474675%40sss.pgh.pa.us>
Precedence: bulk

Stephen Frost <sfrost@snowman.net> writes:
> Yeah, that should also be updated.  Perhaps you'd send an updated patch
> which includes fixing that too and maybe adds clarifying documentation
> to COPY which mentions what happens when RLS is enabled on the relation?

I couldn't find anything in copy.sgml that seemed to need adjustment.
It already says

    If row-level security is enabled for the table, the relevant SELECT
    policies will apply to COPY table TO statements.

Together with the already-mentioned

    COPY table TO copies the same rows as SELECT * FROM ONLY table.

I'd say that the behavior is very clearly specified already.  We just
need to make the code do what the docs say.  So I pushed the patch
without any docs changes.  I did add a test case, because I don't
like back-patching without something that proves that the issue is
relevant to, and corrected in, each branch.

			regards, tom lane