|
1 | 1 | <!-- |
2 | | -$Header: /cvsroot/pgsql/doc/src/sgml/ref/copy.sgml,v 1.14 2000/04/18 23:21:04 momjian Exp $ |
| 2 | +$Header: /cvsroot/pgsql/doc/src/sgml/ref/copy.sgml,v 1.15 2000/04/18 23:43:24 momjian Exp $ |
3 | 3 | Postgres documentation |
4 | 4 | --> |
5 | 5 |
|
@@ -48,7 +48,7 @@ COPY [ BINARY ] <replaceable class="parameter">table</replaceable> [ WITH OIDS ] |
48 | 48 | <listitem> |
49 | 49 | <para> |
50 | 50 | Changes the behavior of field formatting, forcing all data to be |
51 | | -stored or readas binaryobjects rather than as text. |
| 51 | +stored or readin binaryformat rather than as text. |
52 | 52 | </para> |
53 | 53 | </listitem> |
54 | 54 | </varlistentry> |
@@ -193,7 +193,7 @@ ERROR: <replaceable>reason</replaceable> |
193 | 193 | </title> |
194 | 194 | <para> |
195 | 195 | The BINARY keyword will force all data to be |
196 | | - stored/read as binaryobjects rather than as text. It is |
| 196 | + stored/read as binaryformat rather than as text. It is |
197 | 197 | somewhat faster than the normal copy command, but is not |
198 | 198 | generally portable, and the files generated are somewhat larger, |
199 | 199 | although this factor is highly dependent on the data itself. By |
|