Re: Baffling sequential scan plan when index scan would

On Wed, 20 Apr 2005, Jeffrey W. Baker wrote:

> I always thought I would not be the kind of person who writes to this
> list asking why the planner is using a sequential scan.  I always looked
> upon such people as newcomers who would eventually learn the mysterious
> wonders of the Pg query execution planner.
>
> But really, this plan is bizarre!  Why is it scanning sequentially for
> ONE tuple as selected by the primary key?  I even increased stats to
> 1000 and disable seq_scan, but it still insists it cannot do an index
> scan.

What version are you using?  If it's not 8.0.x, I'd guess this is the old
cannot use indexes from cross-integer type comparisons issue, and you may
want to explicitly cast or quote that 2143888.