On Aug 28, 2008, at 6:10 PM, Matthew Dennis wrote:
> I'm not sure I follow. Couldn't you track which statements were
> prepared that called a function and either reprepare (just like
> reindex, recheck, etc) or in the case of dropping a function,
> refuse to drop it because something depends on it?
EXECUTE in PL/pgSQL accepts a string and executes it as a statement.
(That's different from the SQL-level EXECUTE.) I'm not sure how one
would track dependencies there.