Re: Yet another issue with step generation in partition pruning - Mailing list pgsql-hackers

From Etsuro Fujita
Subject Re: Yet another issue with step generation in partition pruning
Date
Msg-id CAPmGK16_U9Cfnys+Q8sS7x78NzZBfgHQESGBKN3i069K9A=5ZQ@mail.gmail.com
Whole thread Raw
In response to Re: Yet another issue with step generation in partition pruning  (Amit Langote <amitlangote09@gmail.com>)
Responses Re: Yet another issue with step generation in partition pruning
List pgsql-hackers
Amit-san,

On Wed, Aug 5, 2020 at 5:13 PM Amit Langote <amitlangote09@gmail.com> wrote:
> Thanks a lot for your time on fixing these multi-column range
> partition pruning issues.  I'm sorry that I failed to notice the
> previous two reports on -bugs for which you committed a fix last week.

No problem.

> On Tue, Aug 4, 2020 at 9:46 PM Etsuro Fujita <etsuro.fujita@gmail.com> wrote:
> > Attached is a patch for fixing this issue.
>
> I have looked at the patch and played around with it using the
> regression tests you've added recently. I was not able to find any
> results that looked surprising.

That's good to hear!  Thanks for reviewing!  Will push the patch tomorrow.

Best regards,
Etsuro Fujita



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: new heapcheck contrib module
Next
From: Robert Haas
Date:
Subject: Re: Allow some recovery parameters to be changed with reload