From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
Cc: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Tablespace permissions issue |
Date: | 2004-06-28 14:08:31 |
Message-ID: | 26294.1088431711@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> writes:
> That way, an admin can force users to NOT use the default tablespace if
> they wish, even though the users have CREATE table rights on the schema.
I think the above statement is nonsensical. Perhaps you are confusing
the notions of "default tablespace for a schema" and "pg_default"?
If the DBA has set a particular default tablespace for a schema, then
that is what he wants users who create in that schema to use --- there
really isn't any other sensible interpretation IMHO. I do not see why
overriding such a choice and forcing the table back into pg_default
should be an operation that is (by default) allowed to unprivileged
users.
Really the only thing special about pg_default is that it is the default
tablespace for template1. If you create a new database and give it a
different default tablespace, then pg_default has got absolutely no
relevance to that database; so I can't see any reason that ordinary
users of that database should be allowed to force their tables back into
pg_default.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-06-28 14:57:47 | Re: Tablespace permissions issue |
Previous Message | Tom Lane | 2004-06-28 13:59:25 | Re: Tablespace permissions issue |