From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | type privileges and default privileges |
Date: | 2011-11-05 14:35:23 |
Message-ID: | 1320503723.28373.5.camel@vanquo.pezone.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
During the closing days of the 9.1 release, we had discussed that we
should add privileges on types (and domains), so that owners can prevent
others from using their types because that would prevent the owners from
changing them in certain ways. (Collations have similar issues and work
quite similar to types, so we could include them in this consideration.)
As I'm plotting to write code for this, I wonder about how to handle
default privileges. For compatibility and convenience, we would still
want to have types with public privileges by default. Should we
continue to hardcode this, as we have done in the past with functions,
for example, or should we use the new default privileges facility to
register the public default privileges in the template database?
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2011-11-05 14:42:55 | plpython extension control files installation |
Previous Message | Noah Misch | 2011-11-05 13:57:43 | Re: Proposal: casts row to array and array to row |