pgsql: Use array_contains_nulls instead of ARR_HASNULL on user-supplied
Use array_contains_nulls instead of ARR_HASNULL on user-supplied arrays.
This applies the fix for bug #5784 to remaining places where we wish
to reject nulls in user-supplied arrays. In all these places, there's
no reason not to allow a null bitmap to be present, so long as none of
the current elements are actually null.
I did not change some other places where we are looking at system catalog
entries or aggregate transition values, as the presence of a null bitmap
in such an array would be suspicious.
Branch
------
master
Details
-------
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=304845075ce0eb9045af50ed32c688a0cb8dd490
Modified Files
--------------
contrib/cube/cube.c | 6 +++---
contrib/ltree/_ltree_gist.c | 4 ++--
contrib/ltree/_ltree_op.c | 6 +++---
contrib/ltree/lquery_op.c | 2 +-
contrib/ltree/ltree_gist.c | 2 +-
src/backend/utils/adt/arrayfuncs.c | 4 ++--
src/backend/utils/adt/arrayutils.c | 2 +-
src/backend/utils/adt/tsrank.c | 2 +-
8 files changed, 14 insertions(+), 14 deletions(-)