From: | "Luke Lonergan" <llonergan(at)greenplum(dot)com> |
---|---|
To: | "Hannu Krosing" <hannu(at)skype(dot)net>, "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
Cc: | "bizgres-general" <bizgres-general(at)pgfoundry(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [Bizgres-general] A Guide to Constraint Exclusion ( |
Date: | 2005-07-14 22:07:22 |
Message-ID: | BEFC302A.8B5E%llonergan@greenplum.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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? Or is it limited to use with constant predicates?
- Luke
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2005-07-14 22:13:05 | Re: [Bizgres-general] A Guide to Constraint Exclusion |
Previous Message | Luke Lonergan | 2005-07-14 22:02:13 | Re: [Bizgres-general] A Guide to Constraint Exclusion |