Skip site navigation (1) Skip section navigation (2)

Re: character encoding in StartupMessage

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: (view raw, whole thread or download thread mbox)
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...


pgsql-hackers by date

Next:From: Jim C. NasbyDate: 2006-02-28 16:22:00
Subject: Re: Vacuum dead tuples that are "between" transactions
Previous:From: Tom LaneDate: 2006-02-28 16:19:02
Subject: Re: character encoding in StartupMessage

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group