Re: Incorrect calculation of path fraction value in MergeAppend
Alexander Korotkov <aekorotkov@gmail.com>
From: Alexander Korotkov <aekorotkov@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>,
Junwang Zhao <zhjwpku@gmail.com>, Andrei Lepikhov <lepihov@gmail.com>, "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>,
Tomas Vondra <tomas@vondra.me>
Date: 2025-05-18T20:47:15Z
Lists: pgsql-bugs
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix tuple_fraction calculation in generate_orderedappend_paths()
- 3d3a81fc24b0 18.0 landed
-
Consider fractional paths in generate_orderedappend_paths
- 6b94e7a6da2f 15.0 cited
On Sun, May 18, 2025 at 5:29 PM Tom Lane <tgl@sss.pgh.pa.us> wrote: > > Alvaro Herrera <alvherre@alvh.no-ip.org> writes: > > 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. > > +1. The bar for causing plan changes in back branches is very high. > Unless you can show that the buggy behavior is causing wrong answers, > it's usually best to leave it alone. Makes sense. Thank you for the clarification. I'll push this to the master only. ------ Regards, Alexander Korotkov Supabase