Throw suitable error for COPY TO STDOUT/FROM STDIN in a SQL function.
authorTom Lane
Sat, 14 Jan 2017 18:27:47 +0000 (13:27 -0500)
committerTom Lane
Sat, 14 Jan 2017 18:27:47 +0000 (13:27 -0500)
A client copy can't work inside a function because the FE/BE wire protocol
doesn't support nesting of a COPY operation within query results.  (Maybe
it could, but the protocol spec doesn't suggest that clients should support
this, and libpq for one certainly doesn't.)

In most PLs, this prohibition is enforced by spi.c, but SQL functions don't
use SPI.  A comparison of _SPI_execute_plan() and init_execution_state()
shows that rejecting client COPY is the only discrepancy in what they
allow, so there's no other similar bugs.

This is an astonishingly ancient oversight, so back-patch to all supported
branches.

Report: https://postgr.es/m/BY2PR05MB2309EABA3DEFA0143F50F0D593780@BY2PR05MB2309.namprd05.prod.outlook.com

src/backend/executor/functions.c

index ae17ea7722cd2e80a03c23fdb7a25f89a2c978d8..3368792cf8f22b229b4d7127f210e4872cd88199 100644 (file)
@@ -498,7 +498,16 @@ init_execution_state(List *queryTree_list,
            else
                stmt = (Node *) pg_plan_query(queryTree, 0, NULL);
 
-           /* Precheck all commands for validity in a function */
+           /*
+            * Precheck all commands for validity in a function.  This should
+            * generally match the restrictions spi.c applies.
+            */
+           if (IsA(stmt, CopyStmt) &&
+               ((CopyStmt *) stmt)->filename == NULL)
+               ereport(ERROR,
+                       (errcode(ERRCODE_FEATURE_NOT_SUPPORTED),
+                   errmsg("cannot COPY to/from client in a SQL function")));
+
            if (IsA(stmt, TransactionStmt))
                ereport(ERROR,
                        (errcode(ERRCODE_FEATURE_NOT_SUPPORTED),