| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Paul Lindner <lindner(at)inuus(dot)com> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Neil Conway <neilc(at)samurai(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Upcoming PG re-releases |
| Date: | 2005-12-04 16:52:45 |
| Message-ID: | 8437.1133715165@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-www |
Paul Lindner <lindner(at)inuus(dot)com> writes:
> On Sun, Dec 04, 2005 at 11:34:16AM -0500, Tom Lane wrote:
>> Paul Lindner <lindner(at)inuus(dot)com> writes:
>>> iconv -c -f UTF8 -t UTF8 -o fixed.sql dump.sql
>>
>> Is that really a one-size-fits-all solution? Especially with -c?
> I'd say yes, and the -c flag is needed so iconv strips out the
> invalid characters.
That's exactly what's bothering me about it. If we recommend that
we had better put a large THIS WILL DESTROY YOUR DATA warning first.
The problem is that the data is not "invalid" from the user's point
of view --- more likely, it's in some non-UTF8 encoding --- and so
just throwing away some of the characters is unlikely to make people
happy.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Brown | 2005-12-04 17:13:28 | Re: Reducing relation locking overhead |
| Previous Message | Paul Lindner | 2005-12-04 16:40:54 | Re: Upcoming PG re-releases |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Maxwell | 2005-12-04 17:19:32 | Upcoming PG re-releases |
| Previous Message | Paul Lindner | 2005-12-04 16:40:54 | Re: Upcoming PG re-releases |