Re: cost_index() and path row estimate.

From: Bernd Helmle <mailings(at)oopsware(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: cost_index() and path row estimate.
Date: 2015-05-04 09:22:33
Message-ID: 6CA3F331D7D7697A9F03A4D1@eje.credativ.lan
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

--On 1. Mai 2015 11:30:51 -0700 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> No. The non-parameterized paths for a given relation must all have the
> same rowcount estimates; otherwise the path comparison logic fails
> fundamentally. Another way to look at it is that every correct path
> will yield the same number of rows in reality; so it would be wrong to
> give a path that makes use of a partial index a rowcount advantage over
> a path that is not using the partial index but nonetheless is enforcing
> exactly the same set of scan restriction clauses.

Thanks for the explanation.

--
Thanks

Bernd

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Evgeniy Shishkin 2015-05-04 09:24:06 Re: JSON data type and schema validation
Previous Message Petr Korobeinikov 2015-05-04 09:21:43 psql :: support for \ev viewname and \sv viewname