| From: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "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:21:31 |
| Message-ID: | 6BCB9D8A16AC4241919521715F4D8BCEA350A1@algol.sollentuna.se |
| 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.
Doesn't this also affect passwords? If so it might be harder to enforce
as the user is often allowed to pick his own password...
//Magnus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2006-02-28 16:22:00 | Re: Vacuum dead tuples that are "between" transactions |
| Previous Message | Tom Lane | 2006-02-28 16:19:02 | Re: character encoding in StartupMessage |