postgres.git / summary / log / commit / refs

commit    ead868059bdf1a8374ba21db3dde766eb00f4fd2
Author:   Bruce Momjian <bruce@momjian.us>
Date:     Tue Dec 06 19:27:09 2005 +0000
First released in: 8.2.0, 8.1.1

    Document method of removing invalid UTF8 escape sequences from dump
    file.  Backpatch to 8.1.X.
    
    Paul Lindner


doc/src/sgml/release.sgml | 20 +++++++++++++++++++- 1 file changed, 19 insertions(+), 1 deletion(-) diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml index c24951e50ab..c7fd4050072 100644 --- a/doc/src/sgml/release.sgml +++ b/doc/src/sgml/release.sgml @@ -1,5 +1,5 @@ <!-- -$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.400.2.1 2005/12/06 18:43:40 momjian Exp $ +$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.400.2.2 2005/12/06 19:27:09 momjian Exp $ Typical markup: @@ -10,6 +10,10 @@ PostgreSQL <productname> pg_[A-Za-z0-9_] <application> [A-Z][A-Z] <type>, <envar>, <literal> &<> use & +non-ascii convert to & escapes + +For new features, add links to the documentation sections. + --> <appendix id="release"> @@ -521,6 +525,20 @@ psql -t -f fixseq.sql db1 | psql -e db1 <type>boolean</type> rather than an <type>integer</type> (Neil) </para> </listitem> + + <listitem> + <para> + Some users are having problems loading <literal>UTF8</> data into + 8.1.X. This is because previous versions allowed invalid <literal>UTF8</> + sequences to be entered into the database, and this release + properly accepts only valid <literal>UTF8</> sequences. One + way to correct a dumpfile is to use <command>iconv -c -f UTF8 -t UTF8</>. + This will remove invalid character sequences. <command>iconv</> + reads the entire input file into memory so it might be necessary to + <command>split</> the dump into multiple smaller files for processing. + </para> + </listitem> + </itemizedlist> </sect2> [parent: 0ebd65ddd40b]