Re: [HACKERS] Superowners
| От | David G. Johnston |
|---|---|
| Тема | Re: [HACKERS] Superowners |
| Дата | |
| Msg-id | CAKFQuwbRHTnZzadCS4kYdRdjqdgO+eEMA8VXi1GK+6d7R8AL4A@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [HACKERS] Superowners (Michael Banck <michael.banck@credativ.de>) |
| Список | pgsql-hackers |
On Thursday, January 26, 2017, Michael Banck <michael.banck@credativ.de> wrote:
On Thu, Jan 26, 2017 at 12:37:44PM -0500, Peter Eisentraut wrote:
> On 1/24/17 8:19 AM, Tom Lane wrote:
> > What about just saying that the database owner has those privileges?
> > After all, the ultimate privilege of an owner is to drop the object
> > (and then remake it as she pleases), and the DB owner has that option
> > w.r.t. the whole database. So I'm not sure we need to invent a new
> > concept.
>
> A database owner does not necessarily have the permission to create a
> new database.
Right.
Would a "TRUNCATE <database>;" (i.e. empty the database, but don't
delete it) make sense/be useful for that maybe?
Conceptually we might already have that.
Drop Owned ...
Though I suspect there might be caveats since indications are it wasn't designed with this particular use case in mind,
David J.
В списке pgsql-hackers по дате отправления: