database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-08 22:02:03 +03:00
Code

Document method of removing invalid UTF8 escape sequences from dump

Browse Source 
file.  Backpatch to 8.1.X.

Paul Lindner
This commit is contained in:
Bruce Momjian 2005-12-06 19:27:09 +00:00
parent 0ebd65ddd4
commit ead868059b
1 changed files with 19 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
doc/src/sgml/release.sgml
View File

@ -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: Typical markup:
@ -10,6 +10,10 @@ PostgreSQL <productname>
pg_[A-Za-z0-9_] <application> pg_[A-Za-z0-9_] <application>
[A-Z][A-Z] <type>, <envar>, <literal> [A-Z][A-Z] <type>, <envar>, <literal>
&<> use & &<> use &
non-ascii convert to & escapes
For new features, add links to the documentation sections.
--> -->
<appendix id="release"> <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) <type>boolean</type> rather than an <type>integer</type> (Neil)
</para> </para>
</listitem> </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> </itemizedlist>
</sect2> </sect2>