Re: getting 'full' names of functions?

Hello Tom,

> > I combined your suggestions into this query I'll be using for now:
>
> > SELECT DISTINCT n.nspname || '.' || p.oid::regprocedure::text FROM
>
> This is flat *wrong*, as you'll soon find if you are working with
> functions in more than one schema. regprocedure already puts a
> schema qualification on the name if one is needed.

You are right. I was more concerned with getting the same number of functions as in pgAdmin III. There were two 'missing' because of pg_function_is_visible:

public.plpgsql_call_handler()
public.plpgsql_validator(oid)

They are obviously relicts from an earlier PostgreSQL-version. Could they cause problems if left be although the new versions are now in pg_catalog which obviously is being searched before all other schemata?

But why is regprocedure not just addding the schema to all of the functions then?

Thank you very much,

Peter
--
Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01