| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| 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-02 14:42:53 |
| Message-ID: | 687683a11c0d8bd0466cedbcb99d098c11f31f97.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
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?
Yours,
Laurenz Albe
| Attachment | Content-Type | Size |
|---|---|---|
| range.V2.diff | text/x-patch | 3.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2023-11-02 15:08:53 | Re: 'pg_global' cannot be used as default_tablespace. |
| Previous Message | Bruce Momjian | 2023-11-02 14:14:58 | Re: Documentation of return values of range functions lower and upper |