From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Default privileges for 7.3 |
Date: | 2002-09-23 15:13:39 |
Message-ID: | 21863.1032794019@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> 7 . 3 O P E N I T E M S
>
> Loading 7.2 pg_dumps
> functions no longer public executable
> languages no longer public usable
Although it's reasonably easy to fix no-privileges problems for
functions after you load a dump, it occurs to me that the same does not
hold for PL languages. If a newly created language doesn't have USAGE
available to public, then any function definitions in your dump are
going to fail, if they belong to non-superusers.
I am thinking that the better course might be to have newly created
languages default to USAGE PUBLIC, at least for a release or two.
We might also consider letting newly created functions default to
EXECUTE PUBLIC. I think this is less essential, but a case could still
be made for it on backwards-compatibility grounds.
If you don't want to hard-wire that behavior, what about a GUC variable
that could be turned on while loading old dumps?
Comments?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-09-23 15:28:48 | Re: Default privileges for 7.3 |
Previous Message | Roberto Fichera | 2002-09-23 15:08:45 | Re: Problem on PG7.2.2 |
From | Date | Subject | |
---|---|---|---|
Next Message | Stephan Szabo | 2002-09-23 15:23:47 | Re: Implementation of LIMIT on DELETE and UPDATE statements |
Previous Message | Tom Lane | 2002-09-23 14:37:00 | Re: Implementation of LIMIT on DELETE and UPDATE statements (rel to 7.2.1) |