|
1 | 1 | <!-- |
2 | | -$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.403 2005/12/0618:45:18 momjian Exp $ |
| 2 | +$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.404 2005/12/0619:26:43 momjian Exp $ |
3 | 3 |
|
4 | 4 | Typical markup: |
5 | 5 |
|
@@ -525,6 +525,20 @@ psql -t -f fixseq.sql db1 | psql -e db1 |
525 | 525 | <type>boolean</type> rather than an <type>integer</type> (Neil) |
526 | 526 | </para> |
527 | 527 | </listitem> |
| 528 | + |
| 529 | + <listitem> |
| 530 | + <para> |
| 531 | + Some users are having problems loading <literal>UTF8</> data into |
| 532 | + 8.1.X. This is because previous versions allowed invalid <literal>UTF8</> |
| 533 | + sequences to be entered into the database, and this release |
| 534 | + properly accepts only valid <literal>UTF8</> sequences. One |
| 535 | + way to correct a dumpfile is to use <command>iconv -c -f UTF8 -t UTF8</>. |
| 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. |
| 539 | + </para> |
| 540 | + </listitem> |
| 541 | + |
528 | 542 | </itemizedlist> |
529 | 543 | </sect2> |
530 | 544 |
|
|