| From: | Neil Chen <carpenter(dot)nail(dot)cz(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | contact(at)yorhel(dot)nl, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #16846: "retrieved too many tuples in a bounded sort" |
| Date: | 2021-02-05 03:07:12 |
| Message-ID: | CAA3qoJm1GCEEVT-9ZjfnF1Yh9yfL5wKRbT+HLKUd4pj-bn8c3w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Feb 5, 2021 at 8:17 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> I poked at this until I found a small modification of the existing
> regression tests that would reach the problematic path with lastTuple
> true. That confirmed that there's a problem, because it gave a flat-out
> wrong answer. I'm not really familiar enough with this code to be sure
> if this is a complete fix, but it fixes the cases we have and it doesn't
> break anything else in our regression tests. So, in view of the fact
> that we have 13.2 release deadline on Monday, I went ahead and pushed it.
> (I did rewrite your comment.)
>
>
That's great, I will also continue to try to check if it is a complete
fix.
Thank you.
--
There is no royal road to learning.
HighGo Software Co.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-02-05 04:02:45 | Re: Postgress 13.x: wrong result for delete with subquery |
| Previous Message | Neil Chen | 2021-02-05 03:02:52 | Re: BUG #16846: "retrieved too many tuples in a bounded sort" |