Re: Fix gin index cost estimation

From: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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 19:53:00
Message-ID: CAPpHfdtVJrC=FeoTudQdfadTa-omn2onk-B7bhCvV_3i3SqHTw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Jan 8, 2023 at 7:08 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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.

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

------
Regards,
Alexander Korotkov

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2023-01-08 20:06:33 Re: [RFC] Add jit deform_counter
Previous Message Justin Pryzby 2023-01-08 19:45:25 Re: Add LZ4 compression in pg_dump