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

From Daniel Westermann (DWE)
Subject Re: Incorrect cost for MergeAppend
Date
Msg-id GV0P278MB04190DA12A364217AA4F99BCD27C2@GV0P278MB0419.CHEP278.PROD.OUTLOOK.COM
Whole thread Raw
In response to Re: Incorrect cost for MergeAppend  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-hackers
Hi,

>Since we have a minor coming up very soon, I think it's not a good idea
>to backpatch right now.  Maybe you can push to master now, and consider
>whether to backpatch later.

>The problem is -- if somebody has an application that gets good plans
>with the current cost model, and you change the cost model and the plans
>become worse, what do they do?  If you change this in a major release,
>this is not an issue because they must test their queries before
>upgrading and if they fail to realize a problem exists then it's their
>fault.  If you change it in a minor release, then those people will be
>very upset that things were changed suddenly, and they may get wary of
>future minor upgrades, which we don't want.

I agree with this, especially as we tell our customers that such changes do not happen from one minor release to another.

Regards
Daniel

pgsql-hackers by date:

Previous
From: James Coleman
Date:
Subject: Re: Parallelize correlated subqueries that execute within each worker
Next
From: Fabrízio de Royes Mello
Date:
Subject: Re: speed up a logical replica setup