From: Tom Lane <tgl@sss.pgh.pa.us>
To: ma100@hotmail.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17172: NaN compare error in hash agg
In-reply-to: <2077133.1630510836@sss.pgh.pa.us>
References: <17172-7505bea9e04e230f@postgresql.org>
 <2077133.1630510836@sss.pgh.pa.us>
Comments: In-reply-to Tom Lane <tgl@sss.pgh.pa.us>
	message dated "Wed, 01 Sep 2021 11:40:36 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2359860.1630618084.1@sss.pgh.pa.us>
Date: Thu, 02 Sep 2021 17:28:04 -0400
Message-ID: <2359861.1630618084@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2359861.1630618084%40sss.pgh.pa.us>
Precedence: bulk

I wrote:
> This has been broken for a very long time.  Do we dare back-patch
> the fix?  Given the lack of complaints, maybe fixing it in HEAD/v14
> is enough.  OTOH, it's not likely that many people have hash indexes
> containing minus NaNs, so maybe it's okay to back-patch.

After further thought I concluded that there's little reason
not to back-patch.  If someone has -NaN in a hash index,
they'd need to re-index if they ever want to find that entry
again ... but it was already true that many queries would not
find that entry.  Hence, pushed to all branches.

			regards, tom lane