Re: int8, primary key, seq scan

Jeff Amiel <jamiel@istreamimaging.com> writes:
> I declared the compared value (draftid) as an int8, why should I have to
> cast it as such in the query to cause the optimizer to use the primary key?

Seems like it should work (and it does work for me, in a quick test with
7.4.5).  Could we see the full text of the problematic function?

            regards, tom lane