| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Treat <rob(at)xzilla(dot)net> |
| 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-18 20:12:12 |
| Message-ID: | 1167135.1750277532@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2025-06-19 00:17:00 | Re: Mention GIN indexes support parallel builds. |
| Previous Message | Robert Treat | 2025-06-18 19:50:19 | Re: Mention GIN indexes support parallel builds. |