|
1 | 1 | <!-- |
2 | | -$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.405 2005/12/06 20:19:17 momjian Exp $ |
| 2 | +$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.406 2005/12/06 20:25:42 momjian Exp $ |
3 | 3 |
|
4 | 4 | Typical markup: |
5 | 5 |
|
@@ -532,10 +532,12 @@ psql -t -f fixseq.sql db1 | psql -e db1 |
532 | 532 | 8.1.X. This is because previous versions allowed invalid <literal>UTF8</> |
533 | 533 | sequences to be entered into the database, and this release |
534 | 534 | properly accepts only valid <literal>UTF8</> sequences. One |
535 | | - way to correct a dumpfile is to use <command>iconv -c -f UTF-8 -t UTF-8</>. |
536 | | - This will remove invalid character sequences. <command>iconv</> |
537 | | - reads the entire input file into memory so it might be necessary to |
538 | | - <command>split</> the dump into multiple smaller files for processing. |
| 535 | + way to correct a dumpfile is to use <command>iconv -c -f UTF-8 -t UTF-8 |
| 536 | + -o cleanfile.sql dumpfile.sql</>. The <literal>-c</> option removes |
| 537 | + invalid character sequences. A diff of the two files will show the |
| 538 | + sequences that are invalid. <command>iconv</> reads the entire input |
| 539 | + file into memory so it might be necessary to <command>split</> the dump |
| 540 | + into multiple smaller files for processing. |
539 | 541 | </para> |
540 | 542 | </listitem> |
541 | 543 |
|
|