On Sun, 18 Oct 2009, Tom Lane wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Sun, Oct 18, 2009 at 1:59 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
>>> Even if country.id is a primary or unique key?
>> Well, we currently don't have any logic for making inferences based on
>> unique constraints.
> Admittedly it's just one case and there's lots more to be done, but it's
> more than nothing. So this is a *potential* argument for trying to trim
> subquery outputs. What I'm not sure about is whether there are common
> cases where this would be applicable below a non-flattenable subquery.
Wow. That's IHMO a major improvement in the optimizer. Is this also valid
In the area of views this might even be a killer feature since one can
define a view with many columns and when only e.g. one is used query is
still optimal. I had today such a situation where I created a new view to
be ~24 times faster (with a lot of left outer joins).
Is the patch only for 8.5 or even backported to 8.4 and 8.3?
In response to
pgsql-performance by date
|Next:||From: Tom Lane||Date: 2009-10-19 17:58:24|
|Subject: Re: Calculation of unused columns |
|Previous:||From: Simon Riggs||Date: 2009-10-19 17:48:58|
|Subject: Re: Calculation of unused columns|