Re: Fix gin index cost estimation - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Fix gin index cost estimation
Date
Msg-id 3583062.1673194082@sss.pgh.pa.us
Whole thread Raw
In response to Re: Fix gin index cost estimation  (Alexander Korotkov <aekorotkov@gmail.com>)
Responses Re: Fix gin index cost estimation  (Alexander Korotkov <aekorotkov@gmail.com>)
List 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



pgsql-hackers by date:

Previous
From: Vik Fearing
Date:
Subject: Re: Todo: Teach planner to evaluate multiple windows in the optimal order
Next
From: Justin Pryzby
Date:
Subject: Re: Progress report of CREATE INDEX for nested partitioned tables