From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Russell Smith <mr-russ(at)pws(dot)com(dot)au> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-bugs(at)postgresql(dot)org, Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Removing pg_auth_members.grantor (was Grantor name gets lost when grantor role dropped) |
Date: | 2007-05-11 20:27:49 |
Message-ID: | 20070511202749.GA3234@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
So the discussion died again with nothing being decided. I see we have
several choices:
1. implement the standard, per Russell suggestion below
2. decide that the standard is braindead and just omit dumping the
grantor when it's no longer available, but don't remove
pg_auth_members.grantor
3. decide that the standard is braindead and remove
pg_auth_members.grantor
Which do people feel should be implemented? I can do whatever we
decide; if no one has a strong opinion on the matter, my opinion is we
do (2) which is the easiest.
Russell Smith wrote:
> My possible suggestion is;
> 1. Implement the standard for revoking only your privileges by default.
> 2. Allow the object owner to revoke privileges assigned by any role, as
> if you drop and recreate the object you can achieve this anyway.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Bojan Jovanovic | 2007-05-11 21:12:05 | Re: BUG #3269: PSQL does not display error output |
Previous Message | Tom Lane | 2007-05-11 20:23:38 | Re: BUG #3269: PSQL does not display error output |
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2007-05-11 21:59:59 | Re: Seq scans roadmap |
Previous Message | Merlin Moncure | 2007-05-11 20:19:51 | Re: [PATCHES] Arrays of Complex Types |