| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
| Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, John DeSoi <desoi(at)pgedit(dot)com>, PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: character encoding in StartupMessage |
| Date: | 2006-02-28 16:19:02 |
| Message-ID: | 15593.1141143542@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
>>> This may be the only solution. Converting everything to UTF-8 has
>>> issues because some encodings are not roundtrip-safe
>> Is this still true?
> I beleive so. If use the ICU Converter Explorer [1] to examine some of
> the encodings we support, they have "Contains ambiguous aliases? TRUE".
Which ones, and are they client-only encodings? If all our server-side
encodings are round-trip safe then I think there's no big issue.
In any case I don't think there's a huge problem if we say that database
and user names had better be chosen from the round-trip-safe subset.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2006-02-28 16:21:31 | Re: character encoding in StartupMessage |
| Previous Message | Tom Lane | 2006-02-28 16:16:27 | Re: Dead Space Map |