docs: minor typo fix for "lower(anymultirange)"
Hackorum builds and tests every patch posted to the lists, not only commitfest submissions. This is Hackorum's own CI rather than the PostgreSQL project's, and it is still under testing - please report anything that looks wrong.
You can run a PostgreSQL built from this patch straight from Docker, with no checkout and no build:
docker run --rm -p 5432:5432 ghcr.io/hackorum-dev/postgres-patch:t49526psql -h localhost -U postgresBuilt from patchset v1 (message #1), July 27, 2026 at 10:56 PM.
Every patchset is also pushed to a branch of our PostgreSQL fork, so you can check out the same tree CI built. Without a PostgreSQL checkout:
git clone --branch t49526_1 https://github.com/hackorum-dev/postgres.gitIn a checkout you already have, add the fork once:
git remote add hackorum https://github.com/hackorum-dev/postgres.gitthen, for this patchset and every later one:
git fetch hackorum t49526_1 && git checkout t49526_1Patchset v1 (message #1) is on t49526_1
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
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
