| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Chuck McDevitt <cmcdevitt(at)greenplum(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: UHC as a server encoding? |
| Date: | 2009-05-01 06:55:27 |
| Message-ID: | 49FA9CDF.2060501@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Chuck McDevitt wrote:
> Why are certain character encodings not legal for the server_encoding?
>
> For example, we allow EUC_KR, but disallow UHC, which is a superset of EUC_KR.
>
> What are the rules for what is or is not allowed as server_encoding?
A server-encoding must have the property that all but the first byte of
a multi-byte character have the high bit set. IOW, by looking at an
arbitrary byte in a string, you must be able to tell if it's part of a
multi-byte character or an independent single byte character.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2009-05-01 07:42:00 | Re: windows shared memory error |
| Previous Message | Robert Treat | 2009-05-01 03:00:55 | Re: Restore deleted rows |