From: | Erki Kaldjärv <erki(at)webware(dot)ee> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pg(at)fastcrypt(dot)com, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: is it possible to get the optimizer to use indexes |
Date: | 2003-12-19 16:00:25 |
Message-ID: | 3FE32099.40901@webware.ee |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Hello,
i got indexes to work with "text_pattern_ops" for locale et_EE.
So instead of:
create index some_index_name on some_table(some_text_field);
nor
create index some_index_name on some_table(some_text_field text_ops);
try to create index as follows:
create index some_index_name on some_table(some_text_field
text_pattern_ops);
Note that text_pattern_ops is available pg >= 7.4.
Regards,
Erki Kaldjärv
Webware OÜ
www.webware.ee
Tom Lane wrote:
>Dave Cramer <pg(at)fastcrypt(dot)com> writes:
>
>
>>So even in a north-american locale, such as en_CA this will be a
>>problem?
>>
>>
>
>If it's not "C" we won't try to optimize LIKE. I know en_US does not
>work (case-insensitive, funny rules about spaces, etc) and I would
>expect en_CA has the same issues.
>
>If you're using 7.4 you have the option to create a special index
>instead of re-initdb'ing your whole database.
>
> regards, tom lane
>
>---------------------------(end of broadcast)---------------------------
>TIP 4: Don't 'kill -9' the postmaster
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | William Yu | 2003-12-19 17:44:17 | Re: why do optimizer parameters have to be set manually? |
Previous Message | Tom Lane | 2003-12-19 15:07:15 | Re: why do optimizer parameters have to be set manually? |