Re: seq scan issue...

["Jeffrey Baker" <jwbaker(at)gmail(dot)com>]

On Thu, Apr 17, 2008 at 11:24 AM, kevin kempter
<kevin(at)kevinkempterllc(dot)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.