| From: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
|---|---|
| To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | AW: like and optimization |
| Date: | 2001-01-22 10:50:20 |
| Message-ID: | 11C1E6749A55D411A9670001FA6879633681CA@sdexcsrv1.f000.d0188.sd.spardat.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > I made a reproduceable example of things going wrong with a "en_US"
> > locale which is the widely-used (single-byte) ISO-8859-1 Latin 1 charset.
>
> en_US uses multi-pass collation rules. It's those collation rules, not
> the charset per se, that causes the problem.
Just to understand things correctly. Is the Like optimization disabled
for all non-ASCII char sets, or (imho correctly) for non charset ordered
collations (LC_COLLATE) ?
Thus can you enable index optimization by simply setting
LC_COLLATE to C if your LANG is not set to C ?
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zeugswetter Andreas SB | 2001-01-22 11:31:10 | AW: FW: Postgresql on win32 |
| Previous Message | Pete Forman | 2001-01-22 10:33:35 | Re: AW: AW: AW: Re: tinterval - operator problems on AIX |