Horton

Re: BUG #19524: NaN handling in btree_gist's float4/float8 opclasses

Bill Kim <billkimjh@gmail.com>

View thread View on postgr.es
From: Bill Kim <billkimjh@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Daniel Gustafsson <daniel@yesql.se>, pgsql-bugs@lists.postgresql.org
Date: 2026-06-29T15:50:11Z
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@sss.pgh.pa.us>님이 작성:

> 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
>

Commits

  1. btree_gist: fix NaN handling in float4/float8 opclasses.