Tom Lane wrote:
> * Fix LIKE indexing optimization for non-ASCII locales
> I've applied a brute-force solution, which is not to do any LIKE
> optimization in non-ASCII locales :-(.
What is a non-ASCII locale ? Anything that is not LC_ALL=ASCII ?
BTW, it would really help if we had a way to query for locale at
like SELECT CURRENT_LOCALE();
How should one find out which locale we are in ?
>From your comment above I assume that you know it ;)
> This is not an ideal answer,
> but perhaps the TODO item should read more like "Figure out how to
> do LIKE indexing optimization in non-ASCII locales".
I think that the cleanest solution should be to define our own locales
that can be doctored to satisfy the LIKE optimisation requirements.
We will probably need something like that in the future anyway as AFAIK
SQL 9x requires ability to have locales applicable on field-to-field
not just one per host.
In response to
pgsql-hackers by date
|Next:||From: Philip Warner||Date: 2001-01-05 13:25:13|
|Subject: Re: [HACKERS] Re: pg_dump return status.. |
|Previous:||From: Hannu Krosing||Date: 2001-01-05 10:49:41|
|Subject: Re: Missing ColLabel tokens|