Remove documentation that CSV didn't handle carriage returns and line

feeds properly.

diff --git a/doc/src/sgml/ref/copy.sgml b/doc/src/sgml/ref/copy.sgml
index e589db6f9ca63217c31dad28a202c9082f8c062e..248d48b412924ef76d6b790dee16c96668d43c58 100644 (file)
--- a/doc/src/sgml/ref/copy.sgml
+++ b/doc/src/sgml/ref/copy.sgml
@@ -497,12 +497,7 @@ COPY <replaceable class="parameter">tablename</replaceable> [ ( <replaceable cla
      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. However, <productname>PostgreSQL</productname> will reject
-     <command>COPY</command> input if any fields contain embedded line
-     end character sequences that do not match the line ending
-     convention used in the CSV file itself. It is generally safer to
-     import data containing embedded line end characters using the
-     text or binary formats rather than CSV.
+     files.
     </para>
    </note>