Re: MergeAppend could consider sorting cheapest child path

From: Andrei Lepikhov <lepihov(at)gmail(dot)com>
To: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
Cc: Alexander Pyhalov <a(dot)pyhalov(at)postgrespro(dot)ru>, Andy Fan <zhihuifan1213(at)163(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Nikita Malakhov <HukuToc(at)gmail(dot)com>
Subject: Re: MergeAppend could consider sorting cheapest child path
Date: 2025-06-03 14:35:57
Message-ID: ddfd1676-7ae9-4a7a-bae0-ca5a6167bda6@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 3/6/2025 16:05, Alexander Korotkov wrote:
> On Tue, Jun 3, 2025 at 4:53 PM Andrei Lepikhov <lepihov(at)gmail(dot)com> wrote:
>> Additionally, as I mentioned earlier, the primary reason for choosing
>> MergeAppend in the regression test was a slight total cost difference
>> that triggered the startup cost comparison.
>> May you show the query and its explain, that is a subject of concern for
>> you?
>
> My point is that difference in total cost is very small. For small
> datasets it could be even within the fuzzy limit. However, in
> practice difference in total time is as big as difference in startup
> time. So, it would be good to make the total cost difference bigger.
For me, it seems like a continuation of the 7d8ac98 discussion. We may
charge a small fee for MergeAppend to adjust the balance, of course.
However, I think this small change requires a series of benchmarks to
determine how it affects the overall cost balance. Without examples it
is hard to say how important this issue is and its worthiness to
commence such work.

--
regards, Andrei Lepikhov

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2025-06-03 14:43:59 Re: pg_upgrade: warn about roles with md5 passwords
Previous Message Tom Lane 2025-06-03 14:34:06 Re: pg_upgrade: warn about roles with md5 passwords