From: | Robert Treat <rob(at)xzilla(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Ben Peachey Higdon <bpeacheyhigdon(at)gmail(dot)com>, pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: Document if width_bucket's low and high are inclusive/exclusive |
Date: | 2025-06-19 01:51:39 |
Message-ID: | CAJSLCQ2aNwXntHfFZdLnrAqrhPUbm7YqytobFOid5mX3VU-C5g@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Wed, Jun 18, 2025 at 4:12 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Treat <rob(at)xzilla(dot)net> writes:
> > On Fri, Feb 28, 2025 at 7:15 AM Ben Peachey Higdon
> > <bpeacheyhigdon(at)gmail(dot)com> wrote:
> >> The current documentation for width_bucket (https://www.postgresql.org/docs/current/functions-math.html) does not mention if 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
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2025-06-19 10:34:41 | Minor documentation fixes related to v18 |
Previous Message | Michael Paquier | 2025-06-19 01:21:22 | Re: Fix inaccurate mention of index comments in CREATE FOREIGN TABLE docs |