Re: LIKE erratic? or unseen DB corruption? - Mailing list pgsql-general

From Tom Lane
Subject Re: LIKE erratic? or unseen DB corruption?
Date
Msg-id 28847.990461340@sss.pgh.pa.us
Whole thread Raw
In response to LIKE erratic? or unseen DB corruption?  (Frank Miles <fpm@u.washington.edu>)
Responses Re: LIKE erratic? or unseen DB corruption?  (Frank Miles <fpm@u.washington.edu>)
List pgsql-general
Frank Miles <fpm@u.washington.edu> writes:
> A direct query gets appropriate rows of data:
> dbname=# select * from partdef where shpname = 'IDC16W';
> ...while the very same query (substituting LIKE for the '=' sign) gets nothing!?

Hm.  Does EXPLAIN show the same kind of plan (index or seq scan) for
both queries?  If not, does forcing the plan choice via ENABLE_xxxSCAN
make a difference?  Do you have locale support turned on, and if so
what locale are you using?

            regards, tom lane

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: LIKE erratic? or unseen DB corruption?
Next
From: Ludovico Romano
Date:
Subject: converting MSAccess to PG with ConvertToPostgreSQL.mdb script of Seva Software