public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bill Kim <[email protected]>
To: Tom Lane <[email protected]>
Cc: Daniel Gustafsson <[email protected]>
Cc: [email protected]
Subject: Re: BUG #19524: NaN handling in btree_gist's float4/float8 opclasses
Date: Tue, 30 Jun 2026 00:50:11 +0900
Message-ID: <CAMQXxcj=HaLUir91J7K_V7mTwehK0nj62tdhCiH8YwSLtp-A3Q@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAMQXxcgbtD2LXfX0tpgvOizxP-XxrCHV2ZDy4By_TZnJMsxXWQ@mail.gmail.com>
<[email protected]>
<CAMQXxch1N=sZ1fsfx57VhTe=8qpmb1K1vnaB5WVyDbAs8bqExg@mail.gmail.com>
<[email protected]>
<CAMQXxch6yrJQdeHQK9Mypa9cmDKjQOc5DJ=SL72pom1djL_OLg@mail.gmail.com>
<[email protected]>
Symptoms are silent wrong answers + EXCLUDE bypass leans me
toward back-patching despite the reindex cost.
Happy with whatever call you make.
2026년 6월 30일 (화) 오전 12:35, Tom Lane <[email protected]>님이 작성:
> Bill Kim <[email protected]> writes:
> > missed the file and please refer to attached.
>
> OK, thanks. I didn't go over this in detail yet, but at first
> glance it looks reasonable.
>
> What I am wondering right now is whether it's better to back-patch
> this or leave well enough alone. Given that we've now had two
> independent complaints, maybe there are enough people using btree_gist
> with NaNs to justify a back-patch, even though it'd force them to
> reindex.
>
> In any case, sneaking it into v19 seems reasonable.
>
> regards, tom lane
>
view thread (10+ messages) latest in thread
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]
Subject: Re: BUG #19524: NaN handling in btree_gist's float4/float8 opclasses
In-Reply-To: <CAMQXxcj=HaLUir91J7K_V7mTwehK0nj62tdhCiH8YwSLtp-A3Q@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