Hmmm, snipped from your reply was the explain plan from the query
where it
was clear you were using two different character data types: bpchat
and
text. That, alone, may have been a problem.
Looking at your defaults, did you do:
initdb --locale=C somepath
I reran initdb --locale=C yesterday
Merlin Moncure [EMAIL PROTECTED] writes:
Here is what I think happened (this might be a bug, might not): Each
night I run initdb but I use a special postgresql.conf which is
optimized for quick data loading. This is copied over the default one
after the server is started. This contains the
Sometime between yesterday and today queries in the form of
select * from t where t.f like 'k%' have been broken so that they
never use the index (on win32, not sure about others).
On win32, at least, they have been broken for a while but this was
due
to a known issue based on the
Sometime between yesterday and today queries in the form of
select * from t where t.f like 'k%' have been broken so that they
never use the index (on win32, not sure about others).
On win32, at least, they have been broken for a while but this was
due
to a known issue based on the
It looks to me like you have an index of type bpchar but are
searching
with type text. I find type conversions very limited with LIKE.
I would create an index on 'vin_no' using a cast to TEXT. This should
work
on both queries.
Not in this case. Just to be sure, I created a new column as
It looks to me like you have an index of type bpchar but are
searching
with type text. I find type conversions very limited with LIKE.
I would create an index on 'vin_no' using a cast to TEXT. This should
work
on both queries.
Not in this case. Just to be sure, I created a new column as
