Thread: pgsql: Tighten pg_get_object_address argument checking

pgsql: Tighten pg_get_object_address argument checking

From
Peter Eisentraut
Date:
Tighten pg_get_object_address argument checking

For publication schemas (OBJECT_PUBLICATION_NAMESPACE) and user
mappings (OBJECT_USER_MAPPING), pg_get_object_address() checked the
array length of the second argument, but not of the first argument.
If the first argument was too long, it would just silently ignore
everything but the first argument.  Fix that by checking the length of
the first argument as well.

Reviewed-by: Amit Kapila <amit.kapila16@gmail.com>
Discussion: https://www.postgresql.org/message-id/flat/caaef70b-a874-1088-92ef-5ac38269c33b%40enterprisedb.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/2da8c4cff39328897aa716a0ba57bdada5aeaf6e

Modified Files
--------------
src/backend/catalog/objectaddress.c          | 10 ++++++++--
src/test/regress/expected/object_address.out | 16 +++++++++++-----
src/test/regress/sql/object_address.sql      |  2 +-
3 files changed, 20 insertions(+), 8 deletions(-)