Re: BUG #16846: "retrieved too many tuples in a bounded sort"

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Neil Chen <carpenter(dot)nail(dot)cz(at)gmail(dot)com>
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 00:17:12
Message-ID: 6068.1612484232@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Neil Chen <carpenter(dot)nail(dot)cz(at)gmail(dot)com> writes:
> Bugs can be fixed with this additional patch, and I have also done tests
> and regression tests. I hope hackers can help me to see if I think wrong or
> miss anything, and I'm sorry that English is not my first language. I hope
> you can tell me if you have any better opinions on the expression of notes,
> thanks.

Hi Neil,

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

Thanks for the patch!

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Neil Chen 2021-02-05 03:02:52 Re: BUG #16846: "retrieved too many tuples in a bounded sort"
Previous Message Mahendra Singh Thalor 2021-02-04 16:42:58 Re: BUG #16846: "retrieved too many tuples in a bounded sort"