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

From Christopher Kings-Lynne
Subject Re: character encoding in StartupMessage
Date
Msg-id 4403F185.2030808@familyhealth.com.au
Whole thread Raw
In response to Re: character encoding in StartupMessage  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: character encoding in StartupMessage
List pgsql-hackers
> I don't see any very nice solution at the moment.  Once we get support
> for per-column locales, it might be possible to declare that the shared
> catalogs are always in UTF8 encoding and get the necessary
> conversions to happen automatically.


At the very least, could we always convert dbnames and store them as 
their own encoding?  That way at least in HTML you can probably mark 
them out as having particular encodings or something...

Chris



pgsql-hackers by date:

Previous
From: Christopher Kings-Lynne
Date:
Subject: ipcclean in 8.1 broken?
Next
From: Hannu Krosing
Date:
Subject: Re: Dead Space Map