Re: estimated rows vs. actual rows - Mailing list pgsql-performance

From Jaime Casanova
Subject Re: estimated rows vs. actual rows
Date
Msg-id c2d9e70e05021319182db34831@mail.gmail.com
Whole thread Raw
In response to Re: estimated rows vs. actual rows  (Josh Berkus <josh@agliodbs.com>)
Responses Re: estimated rows vs. actual rows
Re: estimated rows vs. actual rows
List pgsql-performance
On Sun, 13 Feb 2005 13:41:09 -0800, Josh Berkus <josh@agliodbs.com> wrote:
> Jaime,
>
> > Why is this query using a seq scan rather than a index scan?
>
> Because it thinks a seq scan will be faster.
>
I will suggest him to probe with seq scans disabled.

But, IMHO, if the table has 143902 and it thinks will retrieve 2610
(almost 1.81% of the total). it won't be faster with an index?

i know, i will suggest him to probe to be sure. just an opinion.

regards,
Jaime Casanova

pgsql-performance by date:

Previous
From: Josh Berkus
Date:
Subject: Re: estimated rows vs. actual rows
Next
From: Tom Lane
Date:
Subject: Re: estimated rows vs. actual rows