From: | Russell Smith <mr-russ(at)pws(dot)com(dot)au> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
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: [HACKERS] Removing pg_auth_members.grantor (was Grantor name gets lost when grantor role dropped) |
Date: | 2007-05-15 22:33:19 |
Message-ID: | 464A352F.5010004@pws.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
Alvaro Herrera wrote:
> Alvaro Herrera wrote:
>
>> Alvaro Herrera wrote:
>>
>>
>>> 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
>>>
>>> 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.
>>>
>> Here is a patch implementing this idea, vaguely based on Russell's.
>>
>
> Applied to CVS HEAD, 8.2 and 8.1.
>
> If we want to start tracking the grantor as a shared dependency, and
> have REVOKE work per spec (i.e. only revoke the privileges actually
> granted by the role executing REVOKE), those are separate patches (and
> they should be applied only to HEAD). This patch merely fixes the fact
> that pg_dumpall failed to work for busted databases.
>
>
Should there also be a doc patch for this, the document descriptions
seemed different to what is actually implemented. I'll check that
before I make any further comments.
Russell
From | Date | Subject | |
---|---|---|---|
Next Message | Russell Smith | 2007-05-15 22:42:13 | Re: [HACKERS] Removing pg_auth_members.grantor (was Grantor name gets lost when grantor role dropped) |
Previous Message | Alvaro Herrera | 2007-05-15 20:26:46 | Re: [HACKERS] Removing pg_auth_members.grantor (was Grantor name gets lost when grantor role dropped) |
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2007-05-15 22:34:11 | Re: Seq scans roadmap |
Previous Message | Jim C. Nasby | 2007-05-15 22:29:30 | Re: Managing the community information stream |