| From: | Ondrej Ivanič <ondrej(dot)ivanic(at)gmail(dot)com> |
|---|---|
| To: | "Waldo, Ethan" <ewaldo(at)healthetechs(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: transitive pruning optimization on the right side of a join for partition tables |
| Date: | 2012-09-30 10:31:49 |
| Message-ID: | CAM6mieKYd=vjKLqq_nzpqkrU9pmt2Qtei6iSjZ0+A+DOqr2FQg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi,
On 30 September 2012 16:36, Waldo, Ethan <ewaldo(at)healthetechs(dot)com> wrote:
> Once again I reiterate that I don't have control over the query construction
> and I am currently running postgresql 9.1.5. My question is, does
> postgresql support transitive pruning optimization on the right side of a
> join for partition tables? If so, how do I get that to work? If not, are
> there plans for this and when should a release with this feature be
> expected?
No, postgres is not smart enough. You need to use same condition
("dates"."recorded_on_id" = ...) for myfact table
("myfact"."recorded_on_id" = ) but you do not have control over the
query construction...
--
Ondrej Ivanic
(ondrej(dot)ivanic(at)gmail(dot)com)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ondrej Ivanič | 2012-09-30 10:40:38 | Re: transitive pruning optimization on the right side of a join for partition tables |
| Previous Message | Waldo, Ethan | 2012-09-30 10:17:16 | Re: transitive pruning optimization on the right side of a join for partition tables |