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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Christopher Murtagh <christopher(dot)murtagh(at)mcgill(dot)ca>, postgres general <pgsql-general(at)postgresql(dot)org>
Subject: Re: restore error - language "plperlu" is not trusted
Date: 2003-12-18 00:48:24
Message-ID: 15613.1071708504@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-patches

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Tom Lane wrote:
>> pg_dump has evidently not gotten the word. If we think the backend's
>> behavior is right then we'd better change pg_dump to suppress trying
>> to GRANT permissions on untrusted languages.

> There should not be any permissions, so there should be nothing to dump.

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).

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.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2003-12-18 01:01:23 Re: Function Returning SETOF Problem
Previous Message Ron St-Pierre 2003-12-18 00:42:18 Re: Function Returning SETOF Problem

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2003-12-18 03:35:19 Re: fork/exec patch
Previous Message Peter Eisentraut 2003-12-17 23:16:27 Re: restore error - language "plperlu" is not trusted