| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> |
| Cc: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: possible wierd boolean bug? |
| Date: | 2004-12-14 20:37:31 |
| Message-ID: | 17306.1103056651@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> writes:
> Try it with explain/analyze which reports 4 rows.
I don't see four rows. I do see different results when I add the third
redundant WHERE clause: it switches to a different index and fails to
find the row it should find. I suspect the problem is located in the
btree index scan setup code that I changed to support cross-data-type
comparisons. (7.4 does not fail, but it doesn't try to use the index
fully either.)
I'm on it... thanks for the test case!
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2004-12-14 20:41:13 | Re: bgwriter changes |
| Previous Message | Tom Lane | 2004-12-14 19:40:19 | Re: bgwriter changes |