'Bruce Momjian' <br...@momjian.us> writes: > Well, we can't walk the function tree to know all called functions, and > those they call, so we don't even try.
Inter function dependencies is a hard topic indeed. I still would like to see some kind of progress being made someday. The general case is turing complete tho, because you can use EXECUTE against programatically generated SQL. You could even generate a CREATE FUNCTION command from within a PL function and EXECUTE it then call the created function… and I think I've seen people do that in the past. Still some kind of limited in scope static analysis for the cases where it's possible to do so would be great. With pg_depend tracking so that you know you're doing something wrong at DROP FUNCTION time. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
