| From: | "Markus Wollny" <Markus(dot)Wollny(at)computec(dot)de> |
|---|---|
| To: | "Howard Cole" <howardnews(at)selestial(dot)com> |
| Cc: | "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 14:54:27 |
| Message-ID: | 28011CD60FB1724DBA4442E38277F6264A711C@hermes.computec.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi!
> -----Ursprüngliche Nachricht-----
> Von: Howard Cole [mailto:howardnews(at)selestial(dot)com]
> Gesendet: Dienstag, 6. Dezember 2005 15:38
> An: Markus Wollny
> Cc: PgSql General
> Betreff: Re: [GENERAL] Unicode Corruption and upgrading to
> 8.0.4. to 8.1
> I am avoiding this solution at the moment since the database
> contains binary (ByteA) fields aswell as text fields and I am
> unsure what iconv would do to this data.
Bytea-data in a plain text dump should be quite safe from iconv, as all the problematic characters (decimal value <32 or >126) in the binary string are represented as SQL escaped octets like \###.
Kind regards
Markus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard van den Berg | 2005-12-06 15:01:18 | Re: Temporary disable autovacuum in pgsql 8.1.0 |
| Previous Message | Tom Lane | 2005-12-06 14:49:28 | Re: Temporary disable autovacuum in pgsql 8.1.0 |