| From: | Alexander Staubo <alex(at)purefiction(dot)net> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
| Cc: | daniel(dot)colchete(at)gmail(dot)com, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: New to PostgreSQL, performance considerations |
| Date: | 2006-12-11 09:05:03 |
| Message-ID: | 3462193C-051C-44C5-BBB8-5AA5470BCFE4@purefiction.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Dec 11, 2006, at 04:35 , Tatsuo Ishii wrote:
>> That's not the whole story. UTF-8 and other variable-width encodings
>> don't provide a 1:1 mapping of logical characters to single bytes; in
>> particular, combination characters opens the possibility of multiple
>> different byte sequences mapping to the same code point; therefore,
>> string comparison in such encodings generally cannot be done at the
>> byte level (unless, of course, you first acertain that the strings
>> involved are all normalized to an unambiguous subset of your
>> encoding).
>
> Can you tell me such encodings supported by PostgreSQL other
> than UTF-8?
http://www.postgresql.org/docs/8.1/interactive/
multibyte.html#MULTIBYTE-CHARSET-SUPPORTED
Alexander.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rajesh Kumar Mallah | 2006-12-11 09:19:17 | Re: Postgresql - Threshold value. |
| Previous Message | Ravindran G - TLS, Chennai. | 2006-12-11 07:37:54 | Postgresql - Threshold value. |