On Thu, 2005-07-14 at 15:07 -0700, Luke Lonergan wrote:
> Hannu,
>
> >> My comment was too terse. What I meant was that you can't do dynamic
> >> exclusion based upon the results of a join. i.e. PPUC2
> >
> > but what about _static_ exlusion based on constraints ?
> >
> > I mean if there is a left side table with say a single partition having
> > CHECK(id_order BETWEEN 1 AND 1000)
> > (either originally or left after eliminating other by other constraints)
> >
> > and 3 right side partition with
> > CHECK(key_order BETWEEN 1 AND 1000)
> > CHECK(key_order BETWEEN 1001 AND 2000)
> > CHECK(key_order BETWEEN 2001 AND 3000)
> >
> > then the 3rd one could be eliminated statically from a join on
> > id_order=key_order
>
> I would expect that the 2nd and 3rd partitions would be CE'ed if the basic
> support is there. Does your current implementation include this capability
> Simon?
No
> Or is it limited to use with constant predicates?
Yes.
It's the first time I've thought to compare the constraint predicates on
joined tables based upon the join restriction. That's possible, but
would take some time to work out.
I've argued that such a construct is not common. I'm open to suggestions
about what *is* common...
Best Regards, Simon Riggs
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
