Yes, I got it. Thank you very much for the explanation.
On 23.05.2024 00:17, Tom Lane wrote:
"a.rybakina" writes:
I faced the issue, when the sorting node in the actual information
shows a larger number of tuples than it actually is. And I can not
understand why?
If I'm reading this correctly
"a.rybakina" writes:
> I faced the issue, when the sorting node in the actual information
> shows a larger number of tuples than it actually is. And I can not
> understand why?
If I'm reading this correctly, the sort node you're worrying about
feeds the inner side of a merge join. Merge join
On Thu, 23 May 2024 at 08:48, a.rybakina wrote:
>-> Sort (cost=613.48..632.86 rows=7754 width=8) (actual
> time=7.612..21.214 rows=77531 loops=1)
> Sort Key: broke_down_course.sno, broke_down_course.cno
> Sort Method: quicksort Memory:
