aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2002-10-19 00:22:14 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2002-10-19 00:22:14 +0000
commit44dc9c1faa3bc6dfea71dc9dd7dc83bb642a818c (patch)
tree1cbfd2d139a488cd88546f05d4b4bf629d37e0cd /doc/src
parent4cff161703beb10aab08b614feb9dfffc3860352 (diff)
downloadpostgresql-44dc9c1faa3bc6dfea71dc9dd7dc83bb642a818c.tar.gz
postgresql-44dc9c1faa3bc6dfea71dc9dd7dc83bb642a818c.zip
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.
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/ref/psql-ref.sgml10
1 files changed, 6 insertions, 4 deletions
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 @@
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.78 2002/10/11 23:03:48 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.79 2002/10/19 00:22:14 tgl Exp $
PostgreSQL documentation
-->
@@ -692,6 +692,7 @@ testdb=>
<varlistentry>
<term><literal>\copy <replaceable class="parameter">table</replaceable>
+ [ ( <replaceable class="parameter">column_list</replaceable> ) ]
{ <literal>from</literal> | <literal>to</literal> }
<replaceable class="parameter">filename</replaceable> | stdin | stdout
[ <literal>with</literal> ]
@@ -705,11 +706,12 @@ testdb=>
Performs a frontend (client) copy. This is an operation that
runs an <acronym>SQL</acronym> <xref linkend="SQL-COPY"
endterm="SQL-COPY-title"> 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,
<application>psql</application> 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.
</para>
<para>