Re: Problem with default partition pruning - Mailing list pgsql-hackers

From Amit Langote
Subject Re: Problem with default partition pruning
Date
Msg-id CA+HiwqHX6vL7sx=bb2nU-EgG2dR==DnU7pXwNjHh7cDJDFsc5w@mail.gmail.com
Whole thread Raw
In response to Re: Problem with default partition pruning  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On Wed, Aug 14, 2019 at 12:25 AM Alvaro Herrera
<alvherre@2ndquadrant.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



pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: pg_upgrade fails with non-standard ACL
Next
From: Bruce Momjian
Date:
Subject: Re: pg_upgrade fails with non-standard ACL