From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
Cc: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, jani(dot)rahkola(at)iki(dot)fi, pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: Documentation of return values of range functions lower and upper |
Date: | 2023-11-13 21:08:13 |
Message-ID: | ZVKQPQpo71JeGyQz@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Thu, Nov 2, 2023 at 06:22:59PM -0400, Bruce Momjian wrote:
> On Thu, Nov 2, 2023 at 03:42:53PM +0100, Laurenz Albe wrote:
> > On Thu, 2023-11-02 at 10:14 -0400, Bruce Momjian wrote:
> > > Better, though "Is the range's upper bound unbounded?" makes me cringe.
> > >
> > > Oh, yeah, totally cringe, me too. :-)
> > >
> > > > It is not the bound that is bounded or not, but the range.
> > > >
> > > > How about "Is the range unbounded at the upper end?" or "Does the range
> > > > have no upper bound?"
> > >
> > > I used your "end" idea to modify the patch, attached.
> >
> > There are still some loose ends:
> >
> > - you lost the specification whether it is the upper or the lower bound
> >
> > - "Infinity" is a literal
> >
> > - "-Infinity" is a very unlikely value for an upper bound
> >
> > How about the attached version?
>
> Agreed, yours is much better.
Backpatched to PG 16.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2023-11-14 04:21:50 | Re: Documentation of return values of range functions lower and upper |
Previous Message | Bruce Momjian | 2023-11-13 19:53:55 | Re: 'pg_global' cannot be used as default_tablespace. |