|
1 | 1 | .\" This is -*-nroff-*- |
2 | 2 | .\" XXX standard disclaimer belongs here.... |
3 | | -.\" $Header: /cvsroot/pgsql/src/man/Attic/copy.l,v 1.2 1996/12/11 00:27:09 momjian Exp $ |
| 3 | +.\" $Header: /cvsroot/pgsql/src/man/Attic/copy.l,v 1.3 1997/07/29 21:43:40 momjian Exp $ |
4 | 4 | .TH COPY SQL 11/05/95 PostgreSQL PostgreSQL |
5 | 5 | .SH NAME |
6 | 6 | copy\(em copy data to or from a class from or to a Unix file. |
@@ -41,10 +41,6 @@ than as ASCII text. It is somewhat faster than the normal |
41 | 41 | command, but is not generally portable, and the files generated are |
42 | 42 | somewhat larger, although this factor is highly dependent on the data |
43 | 43 | itself. |
44 | | -When copying in, the |
45 | | -.BR"with oids" |
46 | | -keyword should only be used on an empty database because |
47 | | -the loaded oids could conflict with existing oids. |
48 | 44 | By default, a ASCII |
49 | 45 | .BR copy |
50 | 46 | uses a tab (\\t) character as a delimiter. The delimiter may also be changed |
@@ -169,9 +165,3 @@ yield unexpected results for the naive user. In this case, |
169 | 165 | .SM$PGDATA\c |
170 | 166 | /foo. In general, the full pathname should be used when specifying |
171 | 167 | files to be copied. |
172 | | -.PP |
173 | | -.BR Copy |
174 | | -has virtually no error checking, and a malformed input file will |
175 | | -likely cause the backend to crash. You should avoid using |
176 | | -.BR copy |
177 | | -for input whenever possible. |