|
1 | 1 | <!-- |
2 | | -$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.409 2005/12/08 22:35:44 momjian Exp $ |
| 2 | +$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.410 2005/12/08 22:44:55 momjian Exp $ |
3 | 3 |
|
4 | 4 | Typical markup: |
5 | 5 |
|
@@ -586,16 +586,17 @@ psql -t -f fixseq.sql db1 | psql -e db1 |
586 | 586 |
|
587 | 587 | <listitem> |
588 | 588 | <para> |
589 | | - Some users are having problems loading UTF-8 data into |
590 | | -8.1.X.This is because previous versions allowed invalid UTF-8 byte |
| 589 | + Some users are having problems loading UTF-8 data into 8.1.X. |
| 590 | + This is because previous versions allowed invalid UTF-8 byte |
591 | 591 | sequences to be entered into the database, and this release |
592 | | - properly accepts only valid UTF-8 sequences. One |
593 | | - way to correct a dumpfile is to run the command <command>iconv -c -f UTF-8 -t UTF-8 |
594 | | - -o cleanfile.sql dumpfile.sql</>. The <literal>-c</> option removes |
595 | | - invalid character sequences. A diff of the two files will show the |
596 | | - sequences that are invalid. <command>iconv</> reads the entire input |
597 | | - file into memory so it might be necessary to use <command>split</> |
598 | | - to break up the dump into multiple smaller files for processing. |
| 592 | + properly accepts only valid UTF-8 sequences. One way to correct a |
| 593 | + dumpfile is to run the command <command>iconv -c -f UTF-8 -t |
| 594 | + UTF-8 -o cleanfile.sql dumpfile.sql</>. The <literal>-c</> option |
| 595 | + removes invalid character sequences. A diff of the two files will |
| 596 | + show the sequences that are invalid. <command>iconv</> reads the |
| 597 | + entire input file into memory so it might be necessary to use |
| 598 | + <command>split</> to break up the dump into multiple smaller |
| 599 | + files for processing. |
599 | 600 | </para> |
600 | 601 | </listitem> |
601 | 602 |
|
|