"Bill Schneider" <[EMAIL PROTECTED]> writes:
> This seems to be a well-known and documented issue. Are there already plans
> to fix this in an upcoming release?
Yes.
> Is the problem here in the optimizer itself, or in the parser?
The problem is that the query is interpreted as "int8col int84e
Hello,
I've also come across the bigint/index bug where an index on
table(bigint_col) is ignored for
explain select * from table where bigint_col = 83
results in a "Seq Scan" while
explain select * from table where bigint_col = '83'
and explain select * from table where bigint_col = 83::bigint
