Re: language handlers in public schema?

Andrew Dunstan <andrew@dunslane.net> writes:
> Yeah. I think we'd need to add "where langlcallfoid != 0" so we don't 
> pick up the internal/C/sql handlers. However, on closer inspection it 
> appears that doind all this in pg_dump would be lots more invasive than 
> I first thought.

Why --- what else is needed beyond the addition of those clauses to the
one query?

> me either, but I wonder if we should provide an option on pg_dump to 
> restore function handlers found in public to whatever we decide about 
> the above.

I don't see the need.  If they were in public before, they can stay
there --- or the DBA can run createlang before running pg_restore to
put them where he wants.
        regards, tom lane