|
Home > Archive > PostgreSQL Administration > January 2006 > like vs =
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Stefan Holzheu 2006-01-12, 3:24 am |
| Hallo,
I just encountered a stange behaviour:
The following query gives zero rows.
bitoek=> SELECT name from file where name =
'mitarbeiter/mit/ mitarbeiter_ehemalig
.php';
name
------
(0 Zeilen)
Replacing "=" by like and escaping the underscore gives the row I knew
to be there:
bitoek=> SELECT name from file where name like
'mitarbeiter/mit/ mitarbeiter\_ehemali
g.php';
name
------------------------------------------
mitarbeiter/mit/ mitarbeiter_ehemalig
.php
(1 Zeile)
Other queries with the equal operator do match rows. Am I missing something?
Postgresql: 8.1.1
Fieldtype: text
Database encoding: Latin9
Regards,
Stefan
--
-----------------------------
Dr. Stefan Holzheu
Tel.: 0921/55-5720
Fax.: 0921/55-5709
BayCEER
EDV und Datenbanken
Universitaet Bayreuth
D-95440 Bayreuth
-----------------------------
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
| |
| Tom Lane 2006-01-12, 3:24 am |
| Stefan Holzheu <stefan.holzheu@bayceer.uni-bayreuth.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/pgsq...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
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
| |
| Stefan Holzheu 2006-01-18, 3:24 am |
| Tom Lane schrieb:
> Stefan Holzheu <stefan.holzheu@bayceer.uni-bayreuth.de> writes:
>
>
> 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/pgsq...12/msg00740.php
LC_COLLATE was POSIX
>
> 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.
>
You were right. Query works now. Thanks
Stefan
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>
>
--
-----------------------------
Dr. Stefan Holzheu
Tel.: 0921/55-5720
Fax.: 0921/55-5709
BayCEER
EDV und Datenbanken
Universitaet Bayreuth
D-95440 Bayreuth
-----------------------------
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
|
|
|
|
|