Re: [HACKERS] Superowners - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [HACKERS] Superowners
Date
Msg-id d4990b71-d71c-f3d9-2f83-51cbaca270b6@2ndquadrant.com
Whole thread Raw
In response to Re: [HACKERS] Superowners  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] Superowners  (Michael Banck <michael.banck@credativ.de>)
Re: [HACKERS] Superowners  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
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.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] [PATCH] Rename pg_switch_xlog to pg_switch_wal
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] [PATCH] Rename pg_switch_xlog to pg_switch_wal