| From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, yuzuko <yuzukohosoya(at)gmail(dot)com>, shawn wang <shawn(dot)wang(dot)pg(at)gmail(dot)com>, Shawn Wang <shawn(dot)wang(at)highgo(dot)ca>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Problem with default partition pruning |
| Date: | 2019-08-14 01:12:22 |
| Message-ID: | CA+HiwqHX6vL7sx=bb2nU-EgG2dR==DnU7pXwNjHh7cDJDFsc5w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Aug 14, 2019 at 12:25 AM Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> On 2019-Aug-13, Amit Langote wrote:
>
> > Thanks a lot for revising. Looks neat, except:
> >
> > + * This is a measure of last resort only to be used because the default
> > + * partition cannot be pruned using the steps; regular pruning, which is
> > + * cheaper, is sufficient when no default partition exists.
> >
> > This text appears to imply that the default can *never* be pruned with
> > steps. Maybe, the first sentence should read something like: "...the
> > default cannot be pruned using the steps generated from clauses that
> > contradict the parent's partition constraint".
>
> Thanks! I have pushed it with this change.
Thank you Alvaro. This takes care of all the issues around default
partition pruning reported on this thread. Thanks everyone.
Regards,
Amit
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2019-08-14 02:10:50 | Re: pg_upgrade fails with non-standard ACL |
| Previous Message | Stephen Frost | 2019-08-14 00:28:12 | Re: pg_upgrade fails with non-standard ACL |