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

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



pgsql-hackers by date:

Previous
From: Justin Pryzby
Date:
Subject: Re: Add LZ4 compression in pg_dump
Next
From: Pavel Stehule
Date:
Subject: Re: [RFC] Add jit deform_counter