On 9 January 2013 21:21, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Simon Riggs <simon@2ndQuadrant.com> writes:
>> On 9 January 2013 20:53, Stephen Frost <sfrost@snowman.net> wrote:
>>> * Simon Riggs (simon@2ndQuadrant.com) wrote:
>>>> I think we need to allow a TEMP permission on tablespaces, so that you
>>>> aren't allowed to create normal objects but you can create TEMP
>>>> objects and sort files there.
>
>>> I agree that this would be valuable. Would we end up needing to burn
>>> another bit off the aclmask though? That's certainly been a concern in
>>> the past and I don't recall that we ever improved that situation.
>
>> There already is a TEMP permission, it just only applies to databases
>> at present.
>
> This sounds like rather a lot of work to create a behavior that doesn't
> solve the originally-complained-of usability problem. All it does is
> make things even more complicated, and add an extra step for the DBA
> who's just trying to set temp_tablespaces to something useful.
There is already an extra step to GRANT the CREATE privilege, so how
does this change things?
The whole point of the thread is that that step was omitted.
Oracle (and IIRC others) allow tablespaces to be created as TEMP, so
that nobody can put normal objects in there. That is a useful facility
and there's no way currently in Postgres of setting things up like
that. Hence the proposal.
-- Simon Riggs http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services
