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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Allow the "operand" input of width_bucket() to be NaN
Date: 2025-07-02 15:36:01
Message-ID: 3480079.1751470561@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> writes:
> On Sat, 21 Jun 2025 at 22:21, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Maxim Orlov 2025-07-02 15:38:07 Re: Add 64-bit XIDs into PostgreSQL 15
Previous Message Álvaro Herrera 2025-07-02 15:31:46 Re: ALTER TABLE ALTER CONSTRAINT misleading error message