| From: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
|---|---|
| To: | Gabriel Weinberg <yegg(at)alum(dot)mit(dot)edu> |
| Cc: | 'Bruno Wolff III' <bruno(at)wolff(dot)to>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Sequential Scan Index Bug |
| Date: | 2004-04-07 15:35:02 |
| Message-ID: | 20040407083400.S67613@megazone.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, 7 Apr 2004, Gabriel Weinberg wrote:
> Yes, I thought I had done that, but now that I figured out what was going
> on, I did it for all cases. So it is no longer occurring for me, but it
> still seems like a bug in PostgreSQL. I would expect it to throw an error
> immediately, instead of scanning the table for a value of a different type.
But what if you said id = 4.0? Would you want it to find the id=4 row?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gabriel Weinberg | 2004-04-07 16:41:03 | Re: Sequential Scan Index Bug |
| Previous Message | Gabriel Weinberg | 2004-04-07 13:42:14 | Re: Sequential Scan Index Bug |