| From: | "Markus Wollny" <Markus(dot)Wollny(at)computec(dot)de> |
|---|---|
| To: | "Howard Cole" <howardnews(at)selestial(dot)com>, "PgSql General" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Unicode Corruption and upgrading to 8.0.4. to 8.1 |
| Date: | 2005-12-06 12:48:53 |
| Message-ID: | 28011CD60FB1724DBA4442E38277F6264A6FF6@hermes.computec.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hello!
> -----Ursprüngliche Nachricht-----
> Von: pgsql-general-owner(at)postgresql(dot)org
> [mailto:pgsql-general-owner(at)postgresql(dot)org] Im Auftrag von Howard Cole
> Gesendet: Dienstag, 6. Dezember 2005 13:41
> An: 'PgSql General'
> Betreff: Re: [GENERAL] Unicode Corruption and upgrading to
> 8.0.4. to 8.1
> >> Hi everyone, I have a problem with corrupt UTF-8 sequences in my
> >> 8.0.4 dump which is preventing me from upgrading to 8.1 -
> which spots
> >> the errors and refuses to import the data. Is there some
> SQL command
> >> that I can use to fix or cauterise the sequences in the 8.0.4
> >> database before dumping to 8.1?
> >>
> >> I think the problem arose using invalid client encodings -
> which were
> >> not rejected prior to 8.1.
We experienced the exact same problems. You may solve the problem by feeding the dump through iconv. See my earlier message on this issue
http://archives.postgresql.org/pgsql-general/2005-11/msg00799.php
On top of that you'd be well advised to try dumping using pg_dump of postgresql 8.1.
Kind regards
Markus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rich Doughty | 2005-12-06 13:01:13 | Re: massive performance hit when using "Limit 1" |
| Previous Message | Richard Huxton | 2005-12-06 12:43:06 | Re: massive performance hit when using "Limit 1" |