General Performance Question - Mailing list pgsql-general

From DAVID ROTH
Subject General Performance Question
Date
Msg-id 1653563957.563818.1637244913291@connect.xfinity.com
Whole thread Raw
In response to Re: Execute command in PL/pgSQL function not executing  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: General Performance Question  (Thomas Kellerer <shammat@gmx.net>)
List pgsql-general
I am working on a large Oracle to Postgres migration.
The existing code frequently constructs a string and then uses Oracle's "EXECUTE IMMEDIATE" to run it.
"EXECUTE" has the same functionality in Postgres.

For example:
CREATE or REPLACE FUNCTION djr_foo_fnc (p_emp_no IN number)
RETURN VARCHAR2
AS
v_sql VARCHAR2(1000);
v_name VARCHAR2(30);
BEGIN
v_sql :=            'SELECT name FROM employees';
v_sql := v_sql ||' WHERE employee_number = '||p_emp_no;
EXECUTE IMMEDIATE v_sql INTO v_name;
RETURN v_name;
END;
/

CREATE or REPLACE FUNCTION djr_foo_fnc (p_emp_no IN number)
RETURN VARCHAR2
AS
v_name VARCHAR2(30);
BEGIN
SELECT name INTO v_name FROM employees
WHERE employee_number = p_emp_no;
RETURN v_name;
END;
/

These are oversimplified samples of some very complex queries I need to migrate.

How does the Postgres optimizer handle these 2 formats?
Which format is likely to perform better?
Thanks
Dave

pgsql-general by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: Execute command in PL/pgSQL function not executing
Next
From: Thomas Kellerer
Date:
Subject: Re: General Performance Question