Re: restore error - language "plperlu" is not trusted

Tom Lane wrote:
> Uh, no, because you can say something like
> revoke all on language plperlu from public;
> and end up with non-null lanacl (because it instantiates the default
> assumption that the owner has all privileges).

OK, that needs to be disallowed.

> We could possibly hack the backend to avoid that, but I think pg_dump
> will need the special-case test anyway since it has to be able to
> cope with existing databases, wherein lanacl may be non-null.

So far we know of 1 such database. I'd like to see some more before we
bother about it.