diff --git a/doc/src/sgml/ref/copy.sgml b/doc/src/sgml/ref/copy.sgml index 07e2f45..af15fd1 100644 *** a/doc/src/sgml/ref/copy.sgml --- b/doc/src/sgml/ref/copy.sgml *************** COPY coun *** 419,424 **** --- 419,434 ---- + If row-level security is enabled for the table, COPY + table TO is + internally converted to COPY (SELECT * FROM + table) TO ..., + and the relevant security policies are applied. Currently, + COPY FROM is not supported for tables with row-level + security. Use equivalent INSERT statements instead. + + + Files named in a COPY command are read or written directly by the server, not by the client application. Therefore, they must reside on or be accessible to the database server machine, diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml index be1b684..4fa925c 100644 *** a/doc/src/sgml/ref/pg_dump.sgml --- b/doc/src/sgml/ref/pg_dump.sgml *************** PostgreSQL documentation *** 699,704 **** --- 699,709 ---- to dump the parts of the contents of the table that they have access to. + + Note that if you use this option currently, you probably also want + the dump be in INSERT format, as the + COPY FROM during restore does not support row security. + diff --git a/doc/src/sgml/ref/pg_restore.sgml b/doc/src/sgml/ref/pg_restore.sgml index c906919..ef5bab4 100644 *** a/doc/src/sgml/ref/pg_restore.sgml --- b/doc/src/sgml/ref/pg_restore.sgml *************** *** 527,533 **** Note that this option currently also requires the dump be in INSERT ! format, as COPY TO does not support row security. --- 527,533 ---- Note that this option currently also requires the dump be in INSERT ! format, as COPY FROM does not support row security.