Re: Incorrect cost for MergeAppend - Mailing list pgsql-hackers

From Ashutosh Bapat
Subject Re: Incorrect cost for MergeAppend
Date
Msg-id CAExHW5sOK7WuB2FLcWQ=ON0-6bFR7bbAoHbftzGCg5=aGj7q0w@mail.gmail.com
Whole thread Raw
In response to Re: Incorrect cost for MergeAppend  (David Rowley <dgrowleyml@gmail.com>)
Responses Re: Incorrect cost for MergeAppend
List pgsql-hackers
On Wed, Jan 31, 2024 at 12:12 PM David Rowley <dgrowleyml@gmail.com> wrote:
>
> What is relevant are things like:
>
> For:
> * It's a clear bug and what's happening now is clearly wrong.
> * inheritance/partitioned table plan changes for the better in minor versions
>
> Against:
> * Nobody has complained for 13 years, so maybe it's unlikely anyone is
> suffering too much.
> * Possibility of inheritance/partitioned table plans changing for the
> worse in minor versions
>

That's what I am thinking as well. And the plans that may change for
the worse are the ones where the costs with and without the patch are
close.

Just to be clear, the change is for good and should be committed to
the master. It's the backpatching I am worried about.

--
Best Wishes,
Ashutosh Bapat



pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: Incorrect cost for MergeAppend
Next
From: Peter Eisentraut
Date:
Subject: Re: Should we remove -Wdeclaration-after-statement?