Re: Yet another issue with step generation in partition pruning

2020-08-07 Thread Etsuro Fujita
On Fri, Aug 7, 2020 at 2:55 PM Etsuro Fujita wrote: > On Thu, Aug 6, 2020 at 12:20 AM Etsuro Fujita wrote: > > Will push the patch tomorrow. > > Done. (I didn't have time for this, because I was terribly busy with > other stuff.) I mean I didn't have time for this *yesterday*. Best regards, Et

Re: Yet another issue with step generation in partition pruning

2020-08-06 Thread Etsuro Fujita
On Thu, Aug 6, 2020 at 12:20 AM Etsuro Fujita wrote: > Will push the patch tomorrow. Done. (I didn't have time for this, because I was terribly busy with other stuff.) Best regards, Etsuro Fujita

Re: Yet another issue with step generation in partition pruning

2020-08-05 Thread Etsuro Fujita
Amit-san, On Wed, Aug 5, 2020 at 5:13 PM Amit Langote 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, 2

Re: Yet another issue with step generation in partition pruning

2020-08-05 Thread Amit Langote
Fujita-san, 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. On Tue, Aug 4, 2020 at 9:46 PM Etsuro Fujita wrote: > Commit 13838740f fixed some issu

Yet another issue with step generation in partition pruning

2020-08-04 Thread Etsuro Fujita
Commit 13838740f fixed some issues with step generation in partition pruning, but as I mentioned in [1], I noticed that there is yet another issue: get_steps_using_prefix() assumes that clauses in the passed-in prefix list are sorted in ascending order of their partition key numbers, but the caller