diff --git a/doc/src/sgml/ref/copy.sgml b/doc/src/sgml/ref/copy.sgml
index 2850b4763f2..808355a3fbe 100644
--- a/doc/src/sgml/ref/copy.sgml
+++ b/doc/src/sgml/ref/copy.sgml
@@ -411,6 +411,15 @@ COPY count
to have column privileges on the column(s) listed in the command.
+
+ If row-level security is enabled for the table, the relevant
+ SELECT policies will apply to COPY
+ table> TO statements.
+ 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,
diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml
index 0ca4ad40a43..ab8ec3f47ed 100644
--- a/doc/src/sgml/ref/pg_dump.sgml
+++ b/doc/src/sgml/ref/pg_dump.sgml
@@ -700,6 +700,11 @@ PostgreSQL documentation
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 66a3aa5455a..f357c573149 100644
--- a/doc/src/sgml/ref/pg_restore.sgml
+++ b/doc/src/sgml/ref/pg_restore.sgml
@@ -498,7 +498,7 @@
Note that this option currently also requires the dump be in INSERT
- format, as COPY TO does not support row security.
+ format, as COPY FROM does not support row security.