Mark multirange_constructor0() and multirange_constructor2() strict
authorAlexander Korotkov <akorotkov@postgresql.org>
Fri, 23 Apr 2021 09:57:33 +0000 (12:57 +0300)
committerAlexander Korotkov <akorotkov@postgresql.org>
Fri, 23 Apr 2021 10:25:45 +0000 (13:25 +0300)
commit6bbcff096f932a1fe43ac3208c5c8b0acac29cda
treef73800aea68771aa4cdfa7b19163146906744d1e
parent3f20d5f37086e548c32ddb9d6ae09c2e1ce300ce
Mark multirange_constructor0() and multirange_constructor2() strict

These functions shouldn't receive null arguments: multirange_constructor0()
doesn't have any arguments while multirange_constructor2() has a single array
argument, which is never null.

But mark them strict anyway for the sake of uniformity.

Also, make checks for null arguments use elog() instead of ereport() as these
errors should normally be never thrown.  And adjust corresponding comments.

Catversion is bumped.

Reported-by: Peter Eisentraut
Discussion: https://postgr.es/m/0f783a96-8d67-9e71-996b-f34a7352eeef%40enterprisedb.com
src/backend/commands/typecmds.c
src/backend/utils/adt/multirangetypes.c
src/include/catalog/catversion.h
src/include/catalog/pg_proc.dat