| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
| Cc: | Junwang Zhao <zhjwpku(at)gmail(dot)com>, Andrei Lepikhov <lepihov(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Tomas Vondra <tomas(at)vondra(dot)me>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Incorrect calculation of path fraction value in MergeAppend |
| Date: | 2025-05-18 12:23:06 |
| Message-ID: | 202505181223.ioge4lxntliv@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2025-May-18, Alexander Korotkov wrote:
> I've slightly revised the patch: commit message and one comment. I
> think this is clearly a bugfix, and it should be backpatched. I'm
> going to push and backpatch it if no objections.
I think we mostly avoid backpatching changes that can cause significant
planning changes, because the consequences for existing systems could be
catastrophic -- even if the known plan changes are beneficial. IMO you
need to spend a lot more effort in showing that this can't possibly harm
anything, before backpatching.
Personally I can see getting this in 18beta2 without too much additional
arguing for it. But for 15-17 you'd need a lot more support than is
evident in this thread.
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-05-18 14:28:58 | Re: Incorrect calculation of path fraction value in MergeAppend |
| Previous Message | Alexander Korotkov | 2025-05-18 11:03:49 | Re: Incorrect calculation of path fraction value in MergeAppend |