From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | 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: | 2020-11-12 08:14:12 |
Message-ID: | 16601466752e40543051369fac722c0a200bb4e6.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Wed, 2020-11-11 at 18:19 +0100, Laurenz Albe wrote:
> > Table 9.54 in page
> > https://www.postgresql.org/docs/current/functions-range.html states that the
> > functions lower and upper return NULL if the requested bound is infinite. If
> > the element type of the range contains the special values infinity and
> > -infinity, this is not correct, as those values are returned if explicitly
> > used as either bound.
>
> +1
>
> Perhaps it would be better to say
>
> NULL if the range is empty or has no lower/upper bound
Here is a patch for this.
Yours,
Laurenz Albe
Attachment | Content-Type | Size |
---|---|---|
0001-Improve-upper-lower-documentation-for-ranges.patch | text/x-patch | 1.4 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Wilson | 2020-11-12 14:40:04 | Re: What does "[backends] should seldom or never need to wait for a write to occur" mean? |
Previous Message | Fujii Masao | 2020-11-12 08:05:10 | doc: index items for pg_stat_progress_xxx views |