On Jun 26, 2008, at 10:02, Tom Lane wrote:
> BTW, I don't think you can use that same-length optimization for
> citext. There's no reason to think that upper/lowercase pairs will
> have the same length all the time in multibyte encodings.
I was wondering about that. I had been thinking of canonically-
equivalent stings and combining marks. Doing a quick test it looks
like combining marks are not equivalent. For example, this returns
SELECT 'Ä'::text = 'Ä'::text;
At least with en_US.UTF-8. Hrm. It looks like my client makes them
both canonical, so I've attached a script demonstrating this issue.
Anyway, I was aware of different byte counts for canonical
equivalence, but not for differences between upper- and lowercase
characters. I'd certainly defer to your knowledge of how these things
truly work in PostgreSQL, Tom, and can of course easily remove that
optimization. So, are your certain about this?
Description: application/octet-stream (34 bytes)
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2008-06-26 17:22:22|
|Subject: Re: Regd: TODO Item |
|Previous:||From: Tom Lane||Date: 2008-06-26 17:02:19|
|Subject: Re: Latest on CITEXT 2.0 |