Tom Lane wrote:
Madison Kelly <[EMAIL PROTECTED]> writes:
Can anyone see why the index might not be being used?
You didn't initdb in 'C' locale. You can either re-initdb,
or create a specialized index with a non-default operator class
to support LIKE. See the documentation.
Madison Kelly <[EMAIL PROTECTED]> writes:
>Can anyone see why the index might not be being used?
You didn't initdb in 'C' locale. You can either re-initdb,
or create a specialized index with a non-default operator class
to support LIKE. See the documentation.
regards
> When you do "explain analyze" of a query that you have difficulties
> with, how are the planner's estimates. Are the estimated number of rows
> about equal to the actual number of rows?
Some of them are pretty far off. For example
-> Merge Left Join (cost=9707.71..13993.52 rows=1276 width=1
Hi all,
I have gone back to my index problem from a while ago where I am
trying to do an update with a regex on the WHERE column. If I specifiy a
constant the index is used so that much I know is working.
I've been reading the 7.4 docs and I saw that a B-Tree index *should*
but used when
