From: | Marko Tiikkaja <marko(at)joh(dot)to> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | DROP PRIVILEGES OWNED BY |
Date: | 2014-12-15 00:43:40 |
Message-ID: | 548E2EBC.6040401@joh.to |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
This week I had a problem where I wanted to drop only the privileges a
certain role had in the system, while keeping all the objects. I
couldn't figure out a reasonable way to do that, so I've attached a
patch for this to this email. Please consider it for inclusion into
9.5. The syntax is:
DROP PRIVILEGES OWNED BY role [, ...]
I at some point decided to implement it as a new command instead of
changing DropOwnedStmt, and I think that might have been a mistake. It
might have made more sense to instead teach DROP OWNED to accept a
specification of which things to drop. But the proposal is more
important than such details, I think.
.marko
Attachment | Content-Type | Size |
---|---|---|
drop_privileges_owned.v0.patch | text/plain | 14.7 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2014-12-15 00:48:52 | Re: DROP PRIVILEGES OWNED BY |
Previous Message | Andrew Dunstan | 2014-12-15 00:19:38 | Re: pg_basebackup vs. Windows and tablespaces |