| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com> |
| Cc: | Antonin Houska <ah(at)cybertec(dot)at>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: advanced partition matching algorithm for partition-wise join |
| Date: | 2017-10-12 16:16:59 |
| Message-ID: | CA+TgmoYDcVjkaPyFPWiabe4bHWbiAkOJTF58YSHUCukyxO+apw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Oct 11, 2017 at 7:08 AM, Ashutosh Bapat
<ashutosh(dot)bapat(at)enterprisedb(dot)com> wrote:
> Here's updated patch set based on the basic partition-wise join
> committed. The patchset applies on top of the patch to optimize the
> case of dummy partitioned tables [1].
>
> Right now, the advanced partition matching algorithm bails out when
> either of the joining relations has a default partition.
So is that something you are going to fix?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gourav Kumar | 2017-10-12 16:32:45 | Re: How does postgres store the join predicate for a relation in a given query |
| Previous Message | Robert Haas | 2017-10-12 16:14:30 | Re: GUC for cleanup indexes threshold. |