Re: seq scan issue... - Mailing list pgsql-performance

From Jeffrey Baker
Subject Re: seq scan issue...
Date
Msg-id fd145f7d0804171130g6549ace3u14876385420f8c11@mail.gmail.com
Whole thread Raw
In response to seq scan issue...  (kevin kempter <kevin@kevinkempterllc.com>)
List pgsql-performance
On Thu, Apr 17, 2008 at 11:24 AM, kevin kempter
<kevin@kevinkempterllc.com> wrote:
> Hi List;
>
>  I have a large tble (playback_device) with 6million rows in it. The
> aff_id_tmp1 table has 600,000 rows.
>  - why am I still getting a seq scan ?
>

You're selecting almost all the rows in the product of aff_id_tmp1 *
playback_fragment.  A sequential scan will be far faster than an index
scan.  You can prove this to yourself using 'set enable_seqscan to
false' and running the query again.  It should be much slower.

pgsql-performance by date:

Previous
From: kevin kempter
Date:
Subject: seq scan issue...
Next
From: Rodrigo Gonzalez
Date:
Subject: Re: seq scan issue...