Re: Allow the "operand" input of width_bucket() to be NaN
Dean Rasheed <dean.a.rasheed@gmail.com>
From: Dean Rasheed <dean.a.rasheed@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2025-07-02T06:48:31Z
Lists: pgsql-hackers
On Sat, 21 Jun 2025 at 22:21, Tom Lane <tgl@sss.pgh.pa.us> wrote: > > The attached patch does what was discussed in the pgsql-docs > thread at [1], namely change the four-argument variants of > width_bucket() to allow their first argument to be NaN, > treating that value as larger than any non-NaN. > LGTM. I note that there is no doc update, and I think that is correct, since we never previously documented that NaN wasn't allowed. The new behaviour is what one would have expected, given that we do document that NaN values compare as greater than all non-NaN values. It could even be argued that this is a bug fix, but the lack of prior complaints justifies not back-patching. Regards, Dean
Commits
-
Allow width_bucket()'s "operand" input to be NaN.
- 7374b3a53635 19 (unreleased) landed