Re: Problem with default partition pruning

From: Amit Langote <amitlangote09(at)gmail(dot)com>
To: yuzuko <yuzukohosoya(at)gmail(dot)com>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(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-07-31 08:17:09
Message-ID: CA+HiwqGKaG1TYTrDiENkR+3jdwfuDuNKz5zk9oXe=OTKCYxLAQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello,

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. :)

I've marked it RfC for now.

Thanks,
Amit

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Konstantin Knizhnik 2019-07-31 08:39:47 Re: Built-in connection pooler
Previous Message Richard Guo 2019-07-31 08:06:30 Re: Parallel grouping sets