MIME-Version: 1.0
References: 
 <CAMQXxcgbtD2LXfX0tpgvOizxP-XxrCHV2ZDy4By_TZnJMsxXWQ@mail.gmail.com>
 <FFB7AB27-9334-4F17-BF56-291845F4A9FD@yesql.se>
 <CAMQXxch1N=sZ1fsfx57VhTe=8qpmb1K1vnaB5WVyDbAs8bqExg@mail.gmail.com>
 <1703741.1782745481@sss.pgh.pa.us>
 <CAMQXxch6yrJQdeHQK9Mypa9cmDKjQOc5DJ=SL72pom1djL_OLg@mail.gmail.com>
 <1717564.1782747310@sss.pgh.pa.us>
In-Reply-To: <1717564.1782747310@sss.pgh.pa.us>
From: Bill Kim <billkimjh@gmail.com>
Date: Tue, 30 Jun 2026 00:50:11 +0900
Message-ID: 
 <CAMQXxcj=HaLUir91J7K_V7mTwehK0nj62tdhCiH8YwSLtp-A3Q@mail.gmail.com>
Subject: Re: BUG #19524: NaN handling in btree_gist's float4/float8 opclasses
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Daniel Gustafsson <daniel@yesql.se>, pgsql-bugs@lists.postgresql.org
Content-Type: multipart/alternative; boundary="00000000000099388e0655666a2d"
Archived-At: 
 <https://www.postgresql.org/message-id/CAMQXxcj%3DHaLUir91J7K_V7mTwehK0nj62tdhCiH8YwSLtp-A3Q%40mail.gmail.com>
Precedence: bulk

--00000000000099388e0655666a2d
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Symptoms are silent wrong answers + EXCLUDE bypass leans me
toward back-patching despite the reindex cost.
Happy with whatever call you make.

2026=EB=85=84 6=EC=9B=94 30=EC=9D=BC (=ED=99=94) =EC=98=A4=EC=A0=84 12:35, =
Tom Lane <tgl@sss.pgh.pa.us>=EB=8B=98=EC=9D=B4 =EC=9E=91=EC=84=B1:

> Bill Kim <billkimjh@gmail.com> 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
>

--00000000000099388e0655666a2d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Symptoms are silent wrong answers + EXCLUDE bypass leans m=
e toward=C2=A0back-patching despite the reindex cost. <br>Happy with whatev=
er call you make.</div><br><div class=3D"gmail_quote gmail_quote_container"=
><div dir=3D"ltr" class=3D"gmail_attr">2026=EB=85=84 6=EC=9B=94 30=EC=9D=BC=
 (=ED=99=94) =EC=98=A4=EC=A0=84 12:35, Tom Lane &lt;<a href=3D"mailto:tgl@s=
ss.pgh.pa.us">tgl@sss.pgh.pa.us</a>&gt;=EB=8B=98=EC=9D=B4 =EC=9E=91=EC=84=
=B1:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Bill Kim &l=
t;<a href=3D"mailto:billkimjh@gmail.com" target=3D"_blank">billkimjh@gmail.=
com</a>&gt; writes:<br>
&gt; missed the file and please refer to attached.<br>
<br>
OK, thanks.=C2=A0 I didn&#39;t go over this in detail yet, but at first<br>
glance it looks reasonable.<br>
<br>
What I am wondering right now is whether it&#39;s better to back-patch<br>
this or leave well enough alone.=C2=A0 Given that we&#39;ve now had two<br>
independent complaints, maybe there are enough people using btree_gist<br>
with NaNs to justify a back-patch, even though it&#39;d force them to<br>
reindex.<br>
<br>
In any case, sneaking it into v19 seems reasonable.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 regards, tom lane<br>
</blockquote></div>

--00000000000099388e0655666a2d--