| From: | Bill Kim <billkimjh(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #19524: NaN handling in btree_gist's float4/float8 opclasses |
| Date: | 2026-06-29 15:50:11 |
| Message-ID: | CAMQXxcj=HaLUir91J7K_V7mTwehK0nj62tdhCiH8YwSLtp-A3Q@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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 <tgl(at)sss(dot)pgh(dot)pa(dot)us>님이 작성:
> Bill Kim <billkimjh(at)gmail(dot)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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2026-06-29 23:08:42 | Re: BUG #19524: NaN handling in btree_gist's float4/float8 opclasses |
| Previous Message | Tom Lane | 2026-06-29 15:35:10 | Re: BUG #19524: NaN handling in btree_gist's float4/float8 opclasses |