The following bug has been logged on the website:
Bug reference: 16023
Logged by: William Burke
Email address: william.burke@collins.com
PostgreSQL version: 9.4.0
Operating system: Windows 10 64bit
Description:
Our company has been adding the search_path to all of our functions in order
to tighten up security by using the following syntax in psql - notice I do
not add single quotes around the search_path values:
ALTER FUNCTION function_name(text, text, text) SET search_path=schema1,
pg_temp;
This works fine, however, when we then open the function in pgAdmin 4.13 (by
right clicking on the function from the pgAdmin browser window and choosing
Scripts -> CREATE Script), it is displaying the search path with single
quotes around it (they were added by pgAdmin4 query tool window), as shown
in the sample function below. This throws an error on our "custom type
variable" inside the function every time we try to recompile this function.
If the single quotes around the search_path are removed, the function will
recompile fine without an error. A sample function and sample error are
provided below:
Sample Function as shown in pgAdmin4.13:
CREATE OR REPLACE FUNCTION schema1.function1(
parameter1 text,
parameter2 text,
parameter3 text)
RETURNS record
LANGUAGE 'plpgsql'
COST 100
VOLATILE SECURITY DEFINER
SET search_path='schema1, pg_temp'
AS $BODY$
DECLARE
v_typeValue customType;
END;
$BODY$;
Sample of the error message returned:
ERROR: type "customType" does not exist
LINE 42: v_typeValue customType;
^
SQL state: 42704
Character: 1366
