Stephen Frost <sfrost@snowman.net> writes:
> So I'm at a loss for why there is this insistence on a default role and
> a superuser-explicit-granting based approach that goes beyond "is it
> installed on the filesystem?" and "is it marked as trusted?".
Okay, so it seems like we're down to just this one point of contention.
You feel that the superuser can control what is in the extension library
directory and that that ought to be sufficient control. I disagree
with that, for two reasons:
* ISTM that that's assuming that the DBA and the sysadmin are the same
person (or at least hold identical views on this subject). In many
installations it'd only be root who has control over what's in that
directory, and I don't think it's unreasonable for the DBA to wish
to be able to exercise additional filtering.
* The point of a default role would be for the DBA to be able to
control which database users can install extensions. Even if the
DBA has full authority over the extension library, that would not
provide control over who can install, only over what is available
for any of them to install.
regards, tom lane
