Re: seq scan instead of index scan - Mailing list pgsql-performance

From Scott Marlowe
Subject Re: seq scan instead of index scan
Date
Msg-id dcc563d10912171526q3e341825i429c6627b4f4d3a9@mail.gmail.com
Whole thread Raw
In response to seq scan instead of index scan  (Karl Larsson <karl.larsson47@gmail.com>)
Responses Re: seq scan instead of index scan
List pgsql-performance
On Thu, Dec 17, 2009 at 4:22 PM, Karl Larsson <karl.larsson47@gmail.com> wrote:
> Hello.
>
> I have a problem I don't understand. I hope it's a simple problem and I'm
> just stupid.
>
> When I make a subquery Postgres don't care about my indexes and makes
> a seq scan instead of a index scan. Why?

PostgreSQL uses an intelligent query planner that predicets how many
rows it will get back for each plan and chooses accordingly.  Since a
few dozen rows will all likely fit in the same block, it's way faster
to sequentially scan the table than to use an index scan.

Note that pgsql always has to go back to the original table to get the
rows anyway, since visibility info is not stored in the indexes.

pgsql-performance by date:

Previous
From: Karl Larsson
Date:
Subject: seq scan instead of index scan
Next
From: "Kevin Grittner"
Date:
Subject: Re: seq scan instead of index scan