Re: Fix gin index cost estimation

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
Cc: Ronan Dunklau <ronan(dot)dunklau(at)aiven(dot)io>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Michael Paquier <michael(at)paquier(dot)xyz>
Subject: Re: Fix gin index cost estimation
Date: 2023-01-08 16:08:02
Message-ID: 3583062.1673194082@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alexander Korotkov <aekorotkov(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Pryzby 2023-01-08 16:48:49 Re: Progress report of CREATE INDEX for nested partitioned tables
Previous Message Vik Fearing 2023-01-08 16:06:13 Re: Todo: Teach planner to evaluate multiple windows in the optimal order