Re: Fix gin index cost estimation

Alexander Korotkov <aekorotkov@gmail.com>

From: Alexander Korotkov <aekorotkov@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Ronan Dunklau <ronan.dunklau@aiven.io>, pgsql-hackers@lists.postgresql.org, Michael Paquier <michael@paquier.xyz>
Date: 2023-01-08T19:53:00Z
Lists: pgsql-hackers
On Sun, Jan 8, 2023 at 7:08 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> 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.

Pushed to master, thank you.  I've noticed the reason for
non-backpatching in the commit message.

------
Regards,
Alexander Korotkov



Commits

  1. Improve GIN cost estimation