|
1 | 1 | <!-- |
2 | | -$Header: /cvsroot/pgsql/doc/src/sgml/ref/copy.sgml,v 1.46 2003/05/09 21:19:48 tgl Exp $ |
| 2 | +$Header: /cvsroot/pgsql/doc/src/sgml/ref/copy.sgml,v 1.47 2003/08/17 04:33:02 momjian Exp $ |
3 | 3 | PostgreSQL documentation |
4 | 4 | --> |
5 | 5 |
|
@@ -380,7 +380,7 @@ COPY <replaceable class="parameter">table</replaceable> [ ( <replaceable class=" |
380 | 380 | The file format used for <command>COPY BINARY</command> changed in |
381 | 381 | <application>PostgreSQL</application> 7.4. The new format consists |
382 | 382 | of a file header, zero or more tuples containing the row data, and |
383 | | - a file trailer. |
| 383 | + a file trailer. Headers and data are now in network byte order. |
384 | 384 | </para> |
385 | 385 |
|
386 | 386 | <refsect3> |
@@ -483,6 +483,15 @@ future extension may add a header field that allows per-column format codes |
483 | 483 | to be specified. |
484 | 484 | </para> |
485 | 485 |
|
| 486 | + <para> |
| 487 | +To determine the appropriate binary format for the actual tuple data you |
| 488 | +should consult the <application>PostgreSQL</application> source, in |
| 489 | +particular the <function>*send</> and <function>*recv</> functions for |
| 490 | +the data type (typically found in the <filename>src/backend/utils/adt</filename> |
| 491 | +directory). The <application>contrib/binarycopy</application> module |
| 492 | +can also be used to create an appropriate format file. |
| 493 | + </para> |
| 494 | + |
486 | 495 | <para> |
487 | 496 | If OIDs are included in the file, the OID field immediately follows the |
488 | 497 | field-count word. It is a normal field except that it's not included |
|