On Mon, 4 Aug 2003, Joseph Shraibman wrote:
> Tom Lane wrote:
> > Joseph Shraibman <[EMAIL PROTECTED]> writes:
> >
> >>What percentage of locales have this problem? Does latin1 have this problem?
> >
> >
> > Latin1 is an encoding, not a locale. To a first approximation, I'd say
> > *all* non-C locales have some kind of sorting funny business.
> >
> OK this clears things up a bit. The locale on my production server (redhat) is set
> to
> en_US, which explains why LIKE doesn't use an index. Do I just have to reset the
> locale
> environment variable and restart postgres? What might the side effects of that be?
Nope, changing locales involves dumping reinitting and restoring. Sorry.
:(
> >>And what about my original idea, can LIKE be turned into an = when there are no
> >>wildcards?
> >
> >
> > It does ... if the index-conversion optimization is enabled at all.
>
> Sorry, what is 'index-conversion optimization' and when is it enabled?
I don't know what that is either. Tom?
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
