| From: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
|---|---|
| To: | "Jeffrey W(dot) Baker" <jwbaker(at)acm(dot)org> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Baffling sequential scan plan when index scan would |
| Date: | 2005-04-21 01:06:57 |
| Message-ID: | 20050420180531.U78224@megazone.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Seltenreich | 2005-04-21 01:15:34 | Re: Encoding problem |
| Previous Message | Jeffrey W. Baker | 2005-04-21 00:50:47 | Baffling sequential scan plan when index scan would be best |