On mån, 2012-03-19 at 15:53 -0400, Tom Lane wrote: > This connects somewhat to the discussions we've had in the past about > trying to get not-intended-for-public-use functions out of the > standard search path. Not that you want to put a full visibility > check into the tab-completion query, but if it could simply exclude a > "pg_private" namespace, that probably wouldn't be too expensive.
I wonder if this could be worked out using pg_depend. For example, give me all functions that are not referenced by some object in pg_catalog. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
