Re: Allow the "operand" input of width_bucket() to be NaN - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Allow the "operand" input of width_bucket() to be NaN
Date
Msg-id 3480079.1751470561@sss.pgh.pa.us
Whole thread Raw
In response to Allow the "operand" input of width_bucket() to be NaN  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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



pgsql-hackers by date:

Previous
From: Jianghua Yang
Date:
Subject: Re: [PATCH] initdb: Treat empty -U argument as unset username
Next
From: Maxim Orlov
Date:
Subject: Re: Add 64-bit XIDs into PostgreSQL 15