Re: Fix gin index cost estimation
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alexander Korotkov <aekorotkov@gmail.com>
Cc: Ronan Dunklau <ronan.dunklau@aiven.io>,
pgsql-hackers@lists.postgresql.org,
Michael Paquier <michael@paquier.xyz>
Date: 2023-01-08T16:08:02Z
Lists: pgsql-hackers
Alexander Korotkov <aekorotkov@gmail.com> writes: > I'm going to push this and backpatch to all supported versions if no objections. Push yes, but I'd counsel against back-patching. People don't generally like unexpected plan changes in stable versions, and that's what a costing change could produce. There's no argument that we are fixing a failure or wrong answer here, so it doesn't seem like back-patch material. regards, tom lane
Commits
-
Improve GIN cost estimation
- cd9479af2af2 16.0 landed