From: Jaime Casanova <systemguards@gmail.com>
To: Josh Berkus <josh@agliodbs.com>
Cc: performance pgsql <pgsql-performance@postgresql.org>
Subject: Re: estimated rows vs. actual rows
Date: Sun, 13 Feb 2005 22:18:52 -0500
Message-ID: <c2d9e70e05021319182db34831@mail.gmail.com> (raw)
In-Reply-To: <200502131341.09811.josh@agliodbs.com>
References: <c2d9e70e0502131327c95e63d@mail.gmail.com>
<200502131341.09811.josh@agliodbs.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: systemguards@gmail.com, josh@agliodbs.com
Subject: Re: estimated rows vs. actual rows
In-Reply-To: <c2d9e70e05021319182db34831@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox