| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Paul Lindner <lindner(at)inuus(dot)com> |
| Cc: | andrew(at)supernews(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Differences in UTF8 between 8.0 and 8.1 |
| Date: | 2005-10-27 01:49:48 |
| Message-ID: | 4360323C.2020701@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> However I'm running into another problem now. The command:
>
> iconv -c -f UTF8 -t UTF8
>
> does strip out the invalid characters. However, iconv reads the
> entire file into memory before it writes out any data. This is not so
> good for multi-gigabyte dump files and doesn't allow for it to be used
> in a pipe between pg_dump and psql.
>
> Anyone have any other recommendations? GNU recode might do it, but
> I'm a bit stymied by the syntax. A quick perl script using
> Text::Iconv didn't work either. I'm off to look at some other perl
> modules and will try to create a script so I can strip out the invalid
> characters.
recode UTF-8..UTF-8 < dump_in.sql > dump_out.sql
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-10-27 02:53:13 | Re: BUG #1993: Adding/subtracting negative time intervals |
| Previous Message | Andrej Ricnik-Bay | 2005-10-27 01:40:20 | Re: Differences in UTF8 between 8.0 and 8.1 |