Re: Allow the "operand" input of width_bucket() to be NaN

2025-07-02 Thread Tom Lane
Dean Rasheed writes: > On Sat, 21 Jun 2025 at 22:21, Tom Lane 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 n

Re: Allow the "operand" input of width_bucket() to be NaN

2025-07-01 Thread Dean Rasheed
On Sat, 21 Jun 2025 at 22:21, Tom Lane 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 t

Allow the "operand" input of width_bucket() to be NaN

2025-06-21 Thread Tom Lane
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. While these functions are defined by the SQL standard, it doesn't appear t