[LucaCappelletti94]

DROP FUNCTION refused to drop a function whenever a check constraint, policy or trigger called any function of the same name. Dropping app.f() failed because a policy called public.f(), and dropping f(int, int) failed because a policy called f(id). The cause sat one level down: a check or policy recorded every function carrying the called name, in every schema and with every argument list, and a trigger was matched to its function by bare name.

A call now reaches the functions of that name in the schema it names, or for an unqualified call in pg_catalog and the search path in force where it was written, that accept the number of arguments it passes. Argument types are not inferred, so overloads taking the same number of arguments all stay reachable and their drop stays refused. A trigger is bound when it is created to the function taking no arguments that PostgreSQL would run, and a trigger naming none is refused. The function lists policies and check constraints report narrow accordingly.

This stacks on #143 and retargets to main once #142 and #143 merge.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!