On Wed, Feb 23, 2011 at 12:50 AM, Nathan Boley <npboley(at)gmail(dot)com> wrote:
>> Personally, I think the first thing we ought to do is add a real, bona
>> fide planner hint to override the selectivity calculation manually,
>> maybe something like this:
>> WHERE (x < 5 AND y = 1) SELECTIVITY (0.1);
> If you're going to go that far, why not just collect statistics on
> that specific predicate?
> ie, ANALYZE SELECTIVITY ON tablename (x, y) WHERE (x < 5 AND y = 1);
> Then it won't fall subject to all of the pitfalls that Tom outlines below.
> Selectivities are easy to estimate if we know the predicate. They only
> become hard when they have to work for every possible predicate.
The Enterprise PostgreSQL Company
In response to
pgsql-hackers by date
|Next:||From: Robert Haas||Date: 2011-02-23 14:48:13|
|Subject: Re: WIP: cross column correlation ...|
|Previous:||From: Alvaro Herrera||Date: 2011-02-23 13:46:09|
|Subject: Re: How to extract a value from a record using attnum or attname?|