Re: Weird ..... (a=1 or a=2) <> (a=2 or a=1)

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 17:01:51
Message-ID: 14225.1147798911@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:
>> 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?

> The new table behaves well:

Did you check that you were getting the same indexscan plans there?
(If not, try ANALYZEing the copied table.) You probably were, but
just in case.

This is definitely pretty baffling. I'm getting to the point where
I want to step through the code with a debugger. I assume that's not
very practical on your live server. Would it be feasible at all to
get a physical copy of the database for testing? Alternatively, do
you know C and gdb well enough to try to debug it for yourself?

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Don Y 2006-05-16 17:29:27 Namespace issues
Previous Message Mark Holm 2006-05-16 16:53:54 PGSQL Database Recovery in Portland Oregon Area needed ASAP

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim C. Nasby 2006-05-16 17:23:33 Re: Compression and on-disk sorting
Previous Message Rafael Martinez 2006-05-16 16:53:41 Re: Weird ..... (a=1 or a=2) <> (a=2 or a=1)