That attached patch updates the docs for COPY CSV to include the recently discussed limitation on importing data with embedded line-end characters.
Maybe we also need a TODO to revisit this during the 8.1 cycle, but I don't believe we should do more than this for now.
cheers
andrew
Index: doc/src/sgml/ref/copy.sgml
===================================================================
RCS file: /home/cvsmirror/pgsql/doc/src/sgml/ref/copy.sgml,v
retrieving revision 1.58
diff -c -r1.58 copy.sgml
*** doc/src/sgml/ref/copy.sgml 15 Nov 2004 06:32:15 -0000 1.58
--- doc/src/sgml/ref/copy.sgml 17 Nov 2004 00:39:05 -0000
***************
*** 3,8 ****
--- 3,9 ----
PostgreSQL documentation
-->
+
<refentry id="SQL-COPY">
<refmeta>
<refentrytitle id="sql-copy-title">COPY</refentrytitle>
***************
*** 500,506 ****
CSV mode will both recognize and produce CSV files with quoted
values containing embedded carriage returns and line feeds. Thus
the files are not strictly one line per table row like text-mode
! files.
</para>
</note>
--- 501,511 ----
CSV mode will both recognize and produce CSV files with quoted
values containing embedded carriage returns and line feeds. Thus
the files are not strictly one line per table row like text-mode
! files. <emphasis>PostgreSQL will encounter an error if it reads a
! line end character sequence embedded in a field that does not match
! those used in the CSV file itself. It is generally safer to import
! data containing embedded line end characters using TEXT or BINARY
! rather than CSV format.</emphasis>
</para>
</note>
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
