| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | ma100(at)hotmail(dot)com |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17172: NaN compare error in hash agg |
| Date: | 2021-09-02 21:28:04 |
| Message-ID: | 2359861.1630618084@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2021-09-03 00:31:49 | BUG #17177: Secondary fails to start after upgrade from 13.3 |
| Previous Message | Tom Lane | 2021-09-02 18:52:55 | Re: BUG #17176: Error raised on valid query |