agora inbox for pgsql-docs@postgresql.org
help / color / mirror / Atom feedFrom: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Treat <rob@xzilla.net>
Cc: Ben Peachey Higdon <bpeacheyhigdon@gmail.com>
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: Document if width_bucket's low and high are inclusive/exclusive
Date: Wed, 18 Jun 2025 16:12:12 -0400
Message-ID: <1167135.1750277532@sss.pgh.pa.us> (raw)
In-Reply-To: <CABV9wwPh9+JAYBudAhTY8yPj5VJACA_FpHfEAaHMX1s4z05VkQ@mail.gmail.com>
References: <2BD74F86-5B89-4AC1-8F13-23CED3546AC1@gmail.com>
<CABV9wwPh9+JAYBudAhTY8yPj5VJACA_FpHfEAaHMX1s4z05VkQ@mail.gmail.com>
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 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
view thread (10+ messages) latest in thread
Message-ID: <1167135.1750277532@sss.pgh.pa.us>
Permalink: ../1167135.1750277532@sss.pgh.pa.us/
Also on: postgresql.org/message-id/1167135.1750277532@sss.pgh.pa.us
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: tgl@sss.pgh.pa.us, rob@xzilla.net, bpeacheyhigdon@gmail.com, pgsql-docs@lists.postgresql.org
Subject: Re: Document if width_bucket's low and high are inclusive/exclusive
In-Reply-To: <1167135.1750277532@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox