From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
Cc: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Quick Extensions Question |
Date: | 2011-03-04 19:04:06 |
Message-ID: | 18583.1299265446@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"David E. Wheeler" <david(at)kineticode(dot)com> writes:
> On Mar 4, 2011, at 7:43 AM, Tom Lane wrote:
>> Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> wrote:
>>> What about using the PL terminology here, and calling the property
>>> 'trusted' (default false, so you have to be a superuser to load them)?
>> Hmm. I see your point, but "trusted" seems like it could just as easily
>> be misunderstood. Anybody have any other opinions about the color of
>> that bikeshed?
> The trusted/untrusted differentiation confuses me every single time I try to remember which is which. So how about requires_superuser or install_as_superuser?
I think install_as_superuser might be read to mean "we will run the
script as superuser, whether the calling user is or not". Which in
fact is a facility that might exist someday, making the chance of
confusion even greater.
requires_superuser isn't bad, but I think I'd rather avoid "requires"
here since we're also using that terminology for prerequisite
extensions. How about "must_be_superuser"?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2011-03-04 19:05:00 | Re: file signature for files that make up postgres database |
Previous Message | Dimitri Fontaine | 2011-03-04 17:24:51 | Re: Quick Extensions Question |