Re: why is scan not using index?

kmh496 <kmh496@kornet.net> writes:
> this should be in the FAQ, right?

It probably is ;-).  I'm betting you're getting burnt by a non-C locale
setting, per this gotcha:

     * The default C locale must be used during initdb because it is not
       possible to know the next-greatest character in a non-C locale.
       You can create a special text_pattern_ops index for such cases
       that work only for LIKE indexing.

            regards, tom lane