> 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.
In response to
pgsql-hackers by date
|Next:||From: Tatsuo Ishii||Date: 2011-02-23 06:39:52|
|Subject: Re: Correctly producing array literals for prepared
|Previous:||From: Kevin Grittner||Date: 2011-02-23 05:20:25|
|Subject: Re: SSI bug?|