Re: Document if width_bucket's low and high are inclusive/exclusive - Mailing list pgsql-docs

From Robert Treat
Subject Re: Document if width_bucket's low and high are inclusive/exclusive
Date
Msg-id CAJSLCQ2aNwXntHfFZdLnrAqrhPUbm7YqytobFOid5mX3VU-C5g@mail.gmail.com
Whole thread Raw
In response to Document if width_bucket's low and high are inclusive/exclusive  (Ben Peachey Higdon <bpeacheyhigdon@gmail.com>)
Responses Re: Document if width_bucket's low and high are inclusive/exclusive
List pgsql-docs
On Wed, Jun 18, 2025 at 4:12 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Treat <rob@xzilla.net> writes:
> > On Fri, Feb 28, 2025 at 7:15 AM Ben Peachey Higdon
> > <bpeacheyhigdon@gmail.com> wrote:
> >> The current documentation for width_bucket (https://www.postgresql.org/docs/current/functions-math.html) does not
mentionif the range’s low and high are inclusive or exclusive. 
>
> > I'm not sure it's the most ground breaking thing, but would probably
> > save a bunch of future people from having to gin up an example to test
> > it, so I'd probably update it per the following patch.
>
> Seems reasonable, but do we need to do anything with the other
> version of width_bucket (the one taking an array of lower bounds)?
> Perhaps this change provides enough context, but I'm unsure.
>

Since they are all lower bounds, they all operate the same way, so it
isn't quite as clear that it needs documenting. Are you thinking
something like this?

Returns the number of the bucket in which operand falls given an array
listing the lower bounds (inclusive) of the buckets


Robert Treat
https://xzilla.net



pgsql-docs by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Fix inaccurate mention of index comments in CREATE FOREIGN TABLE docs
Next
From: Fujii Masao
Date:
Subject: Minor documentation fixes related to v18