Re: Problem with default partition pruning

From: Amit Langote <amitlangote09(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: 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-02 01:30:38
Message-ID: CA+HiwqFZXAZwUDtrCsBQ0wt_jA0Ze2zWgcef0nZWFxYFtSdPpA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jul 31, 2019 at 9:49 PM Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
> On 2019-Jul-31, Amit Langote wrote:
> > I noticed that the patch is still marked as "Waiting on Author" ever
> > since Shawn set it that way on June 17. Since Hosoya-san posted
> > updated patches on June 27, the status should've been changed to
> > "Needs Review". Or maybe "Ready for Committer", because the last time
> > I looked, at least the default partition pruning issue seems to be
> > sufficiently taken care of by the latest patch. Whether or not we
> > should apply the other patch (more aggressive use of constraint
> > exclusion by partprune.c on partitioned partitions), I'm not sure, but
> > maybe a committer can decide in an instant. :)
>
> Thanks for the status update. I intend to get this patch pushed before
> the next set of minors.

Thank you Alvaro.

Regards,
Amit

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2019-08-02 01:59:06 Re: The unused_oids script should have a reminder to use the 8000-8999 OID range
Previous Message Michael Paquier 2019-08-02 01:06:03 Re: Fix typos