Peter Eisentraut ab7032b3a8 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		2022-09-21 09:42:22 -04:00
..
backend	Tighten pg_get_object_address argument checking	2022-09-21 09:42:22 -04:00
bin	Suppress variable-set-but-not-used warnings from clang 15.	2022-09-20 12:04:37 -04:00
common
fe_utils
include	Make check_usermap() parameter names consistent.	2022-09-17 16:54:16 -07:00
interfaces
makefiles
pl
port	Include c.h instead of postgres.h in src/port/*p{read,write}*.c	2022-09-17 09:23:49 -07:00
template
test	Tighten pg_get_object_address argument checking	2022-09-21 09:42:22 -04:00
timezone
tools	Revert SQL/JSON features	2022-09-01 17:10:42 -04:00
tutorial	Update copyright for 2022	2022-01-07 19:04:57 -05:00
.gitignore
DEVELOPERS
Makefile
Makefile.global.in
Makefile.shlib
nls-global.mk	Improve frontend error logging style.	2022-04-08 14:55:14 -04:00