Postgres Pro
Downloads
Home   >   mailing lists

LC_COLLATE and index usage - Mailing list pgsql-general

From Forest Wilkinson
Subject LC_COLLATE and index usage
Date
Msg-id k71jbvo3j70mbdfpumf25r95qt9a2vm7kr@4ax.com
Whole thread Raw
Responses How to determine a database cluster's LC_COLLATE setting?  ("Forest Wilkinson" <lyris-pg@tibit.com>)
Re: LC_COLLATE and index usage  (Karsten Hilbert <Karsten.Hilbert@gmx.net>)
Re: LC_COLLATE and index usage  (Andrew Sullivan <andrew@libertyrms.info>)
List pgsql-general
Tree view 
According to the postgres 7.3.2 docs, initializing a database cluster
with LC_COLLATE set to anything other than "C" will disable the use of
indexes during LIKE searches.  This presents a bit of a problem for
me, since the client application I'm writing uses LIKE searches and
ships internationally.  As I understand it, I can have good
performance, or locale-specific ORDER BY output, but not both.  Is
there a plan to remove this limitation?

pgsql-general by date:

Previous
From: eruqamca@yahoo.com (jose arias)
Date:
Subject: bpchar_name
Next
From: "Forest Wilkinson"
Date:
Subject: How to determine a database cluster's LC_COLLATE setting?