docs: minor typo fix for "lower(anymultirange)"

Started by Ian Lawrence Barwickalmost 2 years ago3 messageshackers
Jump to latest
#1Ian Lawrence Barwick
barwick@gmail.com

Hi

Here:

https://www.postgresql.org/docs/current/functions-range.html#MULTIRANGE-FUNCTIONS-TABLE

the description for "lower(anymultirange)":

(NULL if the multirange is empty has no lower bound).

is missing "or" and should be:

(NULL if the multirange is empty or has no lower bound).

Seems to have been omitted with 7539a1b2 (REL_16_STABLE + master).

Very minor issue, but I have seen it and can no longer unsee it.

Regards

Ian Barwick

Attachments:

v1-0001-doc-fix-lower-anymultirange-description.patchtext/x-patch; charset=US-ASCII; name=v1-0001-doc-fix-lower-anymultirange-description.patchDownload+1-2
#2Richard Guo
guofenglinux@gmail.com
In reply to: Ian Lawrence Barwick (#1)
Re: docs: minor typo fix for "lower(anymultirange)"

On Thu, Apr 25, 2024 at 8:40 AM Ian Lawrence Barwick <barwick@gmail.com>
wrote:

Hi

Here:

https://www.postgresql.org/docs/current/functions-range.html#MULTIRANGE-FUNCTIONS-TABLE

the description for "lower(anymultirange)":

(NULL if the multirange is empty has no lower bound).

is missing "or" and should be:

(NULL if the multirange is empty or has no lower bound).

Good catch! I checked the descriptions for "upper(anymultirange)",
"lower(anyrange)" and "upper(anyrange)", and they are all correct. We
should fix this one.

Thanks
Richard

#3Michael Paquier
michael@paquier.xyz
In reply to: Richard Guo (#2)
Re: docs: minor typo fix for "lower(anymultirange)"

On Thu, Apr 25, 2024 at 09:02:34AM +0800, Richard Guo wrote:

Good catch! I checked the descriptions for "upper(anymultirange)",
"lower(anyrange)" and "upper(anyrange)", and they are all correct. We
should fix this one.

+1.
--
Michael