Re: Weird ..... (a=1 or a=2) <> (a=2 or a=1)
| От | Tom Lane |
|---|---|
| Тема | Re: Weird ..... (a=1 or a=2) <> (a=2 or a=1) |
| Дата | |
| Msg-id | 13741.1147797168@sss.pgh.pa.us обсуждение |
| Ответ на | Re: Weird ..... (a=1 or a=2) <> (a=2 or a=1) (Rafael Martinez <r.m.guerrero@usit.uio.no>) |
| Ответы |
Re: Weird ..... (a=1 or a=2) <> (a=2 or a=1)
|
| Список | pgsql-general |
Rafael Martinez <r.m.guerrero@usit.uio.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
В списке pgsql-general по дате отправления: