From 44dc9c1faa3bc6dfea71dc9dd7dc83bb642a818c Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Sat, 19 Oct 2002 00:22:14 +0000 Subject: Fix psql's \copy to accept table names containing schemas, as well as a column list. Bring its parsing of quoted names and quoted strings somewhat up to speed --- I believe it now handles all non-error cases the same way the backend would, but weird boundary conditions are not necessarily done the same way. --- doc/src/sgml/ref/psql-ref.sgml | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/ref/psql-ref.sgml b/doc/src/sgml/ref/psql-ref.sgml index d232ef895ac..6e3525d7687 100644 --- a/doc/src/sgml/ref/psql-ref.sgml +++ b/doc/src/sgml/ref/psql-ref.sgml @@ -1,5 +1,5 @@ @@ -692,6 +692,7 @@ testdb=> \copy table + [ ( column_list ) ] { from | to } filename | stdin | stdout [ with ] @@ -705,11 +706,12 @@ testdb=> Performs a frontend (client) copy. This is an operation that runs an SQL command, but instead of the backend's - reading or writing the specified file, and consequently - requiring backend access and special user privilege, as well as - being bound to the file system accessible by the backend, + reading or writing the specified file, psql reads or writes the file and routes the data between the backend and the local file system. + This means that file accessibility and privileges are those + of the local user, not the server, and no SQL superuser + privileges are required. -- cgit v1.2.3