From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Christopher Murtagh <christopher(dot)murtagh(at)mcgill(dot)ca> |
Cc: | postgres general <pgsql-general(at)postgresql(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net> |
Subject: | Re: restore error - language "plperlu" is not trusted |
Date: | 2003-12-17 18:45:52 |
Message-ID: | 9049.1071686752@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-patches |
Christopher Murtagh <christopher(dot)murtagh(at)mcgill(dot)ca> writes:
> [ pg_dump script failed with ]
> ERROR: language "plperlu" is not trusted
> and it gave a line number, which contained the following:
> GRANT ALL ON LANGUAGE plperlu TO postgres WITH GRANT OPTION;
Hm. The backend flat-out rejects all attempts at GRANT on untrusted
languages, even if you are superuser and the grantee is too. I'm not
totally sure about the rationale for that (Peter?) but in any case
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.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Stephan Szabo | 2003-12-17 18:54:26 | Re: Permissions issue? |
Previous Message | Christopher Murtagh | 2003-12-17 18:38:38 | Re: Permissions issue? |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2003-12-17 18:49:31 | Re: [PATCHES] Double Backslash example patch |
Previous Message | Tom Lane | 2003-12-17 18:07:35 | Re: [PATCHES] Double Backslash example patch |