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?