From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Rafael Martinez <r(dot)m(dot)guerrero(at)usit(dot)uio(dot)no> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Weird ..... (a=1 or a=2) <> (a=2 or a=1) |
Date: | 2006-05-16 16:32:48 |
Message-ID: | 13741.1147797168@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Rafael Martinez <r(dot)m(dot)guerrero(at)usit(dot)uio(dot)no> writes:
> On Tue, 2006-05-16 at 11:14 -0400, Tom Lane wrote:
>> I suspect this may be a question of a corrupt index, in which case
>> REINDEXing the index being used would fix it.
> This is what I thought when I found out the problem. So before I sent my
> first e-mail I executed a "reindex index tickets6" but it did not help.
So much for that theory. If you copy the table (create table foo as
select * from tickets) and build a similar index on the copy, does the
behavior persist in the copy?
I'm wondering a little bit about encoding issues. What encoding does
the database have (see \l) and what do SHOW LC_COLLATE and SHOW LC_CTYPE
show?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Rafael Martinez | 2006-05-16 16:53:41 | Re: Weird ..... (a=1 or a=2) <> (a=2 or a=1) |
Previous Message | Rafael Martinez | 2006-05-16 16:26:05 | Re: Weird ..... (a=1 or a=2) <> (a=2 or a=1) |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2006-05-16 16:33:31 | Re: [PATCHES] .pgpass file and unix domain sockets |
Previous Message | Andrew Dunstan | 2006-05-16 16:27:42 | Re: Compression and on-disk sorting |