Re: Allow the "operand" input of width_bucket() to be NaN
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dean Rasheed <dean.a.rasheed@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2025-07-02T15:36:01Z
Lists: pgsql-hackers
Dean Rasheed <dean.a.rasheed@gmail.com> writes: > 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. Pushed, thanks for looking at it. > It could even be argued that this is a bug fix, but the lack of prior > complaints justifies not back-patching. Yeah, that was my feeling as well. regards, tom lane
Commits
-
Allow width_bucket()'s "operand" input to be NaN.
- 7374b3a53635 19 (unreleased) landed