From: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Upcoming PG re-releases |
Date: | 2005-12-07 03:45:51 |
Message-ID: | Pine.LNX.4.58.0512071442040.21925@linuxworld.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-www |
Hi,
On Tue, 6 Dec 2005, Bruce Momjian wrote:
>
> Nice, updated.
>
> ---------------------------------------------------------------------------
>
I think my suggestion from the other day is useful also.
---
Omar Kilani and I have spent a few hours looking at the problem. For
situations where there is a lot of invalid encoding, manual fixing is just
not viable. The vim project has a kind of fuzzy encoding conversion which
accounts for a lot of the non-UTF8 sequences in UTF8 data. You can use vim
to modify your text dump as follows:
vim -c ":wq! ++enc=utf8 fixed.dump" original.dump
---
I think this is a viable option for people with a non-trivial amount of
data and don't see manual fixing or potentially losing data as a viable
option.
Thanks,
Gavin
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Fuhr | 2005-12-07 03:47:39 | Re: row is too big: size 8916, maximum size 8136 |
Previous Message | Tom Lane | 2005-12-07 03:19:44 | Re: row is too big: size 8916, maximum size 8136 |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2005-12-07 04:37:56 | Re: Upcoming PG re-releases |
Previous Message | Josh Berkus | 2005-12-07 01:02:09 | Re: Integration Requirements |