| From: | Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com> |
|---|---|
| To: | Amit Langote <amitlangote09(at)gmail(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Yet another issue with step generation in partition pruning |
| Date: | 2020-08-05 15:20:50 |
| Message-ID: | CAPmGK16_U9Cfnys+Q8sS7x78NzZBfgHQESGBKN3i069K9A=5ZQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Amit-san,
On Wed, Aug 5, 2020 at 5:13 PM Amit Langote <amitlangote09(at)gmail(dot)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(dot)fujita(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2020-08-05 15:41:49 | Re: Allow some recovery parameters to be changed with reload |
| Previous Message | Robert Haas | 2020-08-05 14:08:50 | Re: new heapcheck contrib module |