Re: Upcoming PG re-releases - Mailing list pgsql-hackers

From Gavin Sherry
Subject Re: Upcoming PG re-releases
Date
Msg-id Pine.LNX.4.58.0512071442040.21925@linuxworld.com.au
Whole thread Raw
In response to Re: Upcoming PG re-releases  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Upcoming PG re-releases  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
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


pgsql-hackers by date:

Previous
From: "Uwe C. Schroeder"
Date:
Subject: Re: [GENERAL] 8.1, OID's and plpgsql
Next
From: Michael Fuhr
Date:
Subject: Re: row is too big: size 8916, maximum size 8136