database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-05 23:56:58 +03:00
Code

Update iconv wording, per Peter.

Browse Source
This commit is contained in:
Bruce Momjian 2005-12-06 21:01:32 +00:00
parent 494d1f1497
commit c90f02316e
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.400.2.4 2005/12/06 20:26:02 momjian Exp $
$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.400.2.5 2005/12/06 21:01:32 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>