| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stefan Holzheu <stefan(dot)holzheu(at)bayceer(dot)uni-bayreuth(dot)de> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: like vs = |
| Date: | 2006-01-12 05:02:15 |
| Message-ID: | 1239.1137042135@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Stefan Holzheu <stefan(dot)holzheu(at)bayceer(dot)uni-bayreuth(dot)de> writes:
> Other queries with the equal operator do match rows. Am I missing something?
> Postgresql: 8.1.1
> Fieldtype: text
> Database encoding: Latin9
What LC_COLLATE locale are you using? Your report looks a whole lot
like the recently identified problem with locales that think that some
not-bitwise-identical strings are "equal", as in this thread:
http://archives.postgresql.org/pgsql-general/2005-12/msg00740.php
If the same queries return sane results after doing set enable_indexscan
= off, then that's probably what the problem is. If so, updating to
8.1.2 and REINDEXing should fix it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-01-12 05:07:05 | Re: Rule for updating ipaddress on insertion |
| Previous Message | navicat | 2006-01-12 04:34:27 | Navicat PostgreSQL Manager for Windows (ver. 7.1.8) is now available |