Re: seqscan for 100 out of 3M rows, index present

From: Willy-Bas Loos <willybas(at)gmail(dot)com>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: seqscan for 100 out of 3M rows, index present
Date: 2013-06-26 20:36:10
Message-ID: CAHnozTiLdn=1XH7X4XyUoD3e=n2sXt=RUCZ3KWr-f6W8WK5SFQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Wed, Jun 26, 2013 at 10:31 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:

>
> Why is it retrieving 3.1 million, when it only needs 17?
>
>
> that's because of the sequential scan, it reads all the data.

cheers,

willy-bas
--
"Quality comes from focus and clarity of purpose" -- Mark Shuttleworth

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Victor Yegorov 2013-06-26 20:46:27 Re: seqscan for 100 out of 3M rows, index present
Previous Message Jeff Janes 2013-06-26 20:31:29 Re: seqscan for 100 out of 3M rows, index present