Re: character encoding in StartupMessage
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Martijn van Oosterhout <kleptog@svana.org>
Cc: Christopher Kings-Lynne <chriskl@familyhealth.com.au>, John DeSoi <desoi@pgedit.com>, PG Hackers <pgsql-hackers@postgresql.org>
Date: 2006-02-28T16:19:02Z
Lists: 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