Re: character encoding in StartupMessage - Mailing list pgsql-hackers

From Tom Lane
Subject Re: character encoding in StartupMessage
Date
Msg-id 15593.1141143542@sss.pgh.pa.us
Whole thread Raw
In response to Re: character encoding in StartupMessage  (Martijn van Oosterhout <kleptog@svana.org>)
Responses Re: character encoding in StartupMessage
Re: character encoding in StartupMessage
List pgsql-hackers
Martijn van Oosterhout <kleptog@svana.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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Dead Space Map
Next
From: "Jim C. Nasby"
Date:
Subject: Re: Vacuum dead tuples that are "between" transactions