mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update iconv wording, per Peter.

Browse Source
This commit is contained in:
Bruce Momjian 2005-12-06 21:00:53 +00:00
parent 371879ca8e
commit 3001b4697d
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -1,5 +1,5 @@
<!--
$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.406 2005/12/06 20:25:42 momjian Exp $
$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.407 2005/12/06 21:00:53 momjian Exp $
Typical markup:
@ -528,16 +528,16 @@ psql -t -f fixseq.sql db1 | psql -e db1
<listitem>
<para>
Some users are having problems loading <literal>UTF8</> data into
8.1.X. This is because previous versions allowed invalid <literal>UTF8</>
Some users are having problems loading UTF-8 data into
8.1.X. This is because previous versions allowed invalid UTF-8 byte
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 UTF-8 -t UTF-8
properly accepts only valid UTF-8 sequences. One
way to correct a dumpfile is to run the command <command>iconv -c -f UTF-8 -t UTF-8
-o cleanfile.sql dumpfile.sql</>. The <literal>-c</> option removes
invalid character sequences. A diff of the two files will show the
sequences that are invalid. <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.
sequences that are invalid. <command>iconv</> reads the entire input
file into memory so it might be necessary to use <command>split</>
to break up the dump into multiple smaller files for processing.
</para>
</listitem>