"Bill Schneider" <bschneider@vecna.com> 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 int84eq int4const"
and int84eq is not one of the operators in the index's opclass. The
planned fix is to get rid of int84eq (and most other cross-datatype
operators) so that the parser is forced to select plain int8eq and
up-convert the literal to int8.
See past discussions of numeric coercion rules in pgsql-hackers archives
if you want to know more about why this is a difficult issue.
regards, tom lane