public inbox for [email protected]
help / color / mirror / Atom feedFrom: Alexander Korotkov <[email protected]>
To: Tom Lane <[email protected]>
Cc: Ronan Dunklau <[email protected]>
Cc: [email protected]
Cc: Michael Paquier <[email protected]>
Subject: Re: Fix gin index cost estimation
Date: Sun, 8 Jan 2023 22:53:00 +0300
Message-ID: <CAPpHfdtVJrC=FeoTudQdfadTa-omn2onk-B7bhCvV_3i3SqHTw@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <3188617.44csPzL39Z@aivenronan>
<CAPpHfdtFYZjv41djYjNcJUuZhDKUu9eJSthKmmDWE-azAZjn5g@mail.gmail.com>
<10184681.nUPlyArG6x@aivenlaptop>
<4787929.31r3eYUQgx@aivenlaptop>
<CAPpHfdvYCtwxTBNmvz6_MDNCDDBBNW6n2VzE3=Wy0m6pEvCd+g@mail.gmail.com>
<[email protected]>
On Sun, Jan 8, 2023 at 7:08 PM Tom Lane <[email protected]> wrote:
> Alexander Korotkov <[email protected]> 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
view thread (3+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: Fix gin index cost estimation
In-Reply-To: <CAPpHfdtVJrC=FeoTudQdfadTa-omn2onk-B7bhCvV_3i3SqHTw@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox