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

From Kevin Grittner
Subject Re: seq scan instead of index scan
Date
Msg-id 4B2A6A6A020000250002D750@gw.wicourts.gov
Whole thread Raw
In response to seq scan instead of index scan  (Karl Larsson <karl.larsson47@gmail.com>)
List pgsql-performance
Karl Larsson <karl.larsson47@gmail.com> wrote:

> When I make a subquery Postgres don't care about my indexes and
> makes a seq scan instead of a index scan. Why?

>  Total runtime: 0.133 ms

Because it thinks that it's faster that way with the particular data
you now have in your tables.  With more data, it might think some
other plan is faster.  It's running in less than 1/7500 second --
how sure are you that it would be significantly faster another way?

-Kevin

pgsql-performance by date:

Previous
From: Scott Marlowe
Date:
Subject: Re: seq scan instead of index scan
Next
From: Karl Larsson
Date:
Subject: Re: seq scan instead of index scan