From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
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, mr-russ(at)pws(dot)com(dot)au, 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-04 19:41:45 |
Message-ID: | 20070504194145.GN1504@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
* Alvaro Herrera (alvherre(at)commandprompt(dot)com) wrote:
> I took a look, and concluded that the only bit of code that uses the
> grantor at all is pg_dumpall.
>
> Does this means we can remove it altogether? In back branches, we would
> take out the pg_dumpall code.
I don't have time right at the moment (leaving shortly and will be gone
all weekend) but what I would do is check the SQL standard, especially
the information schema, for any requirement to track the grantor. Much
of what I did was based on the standard so that may have been the
instigation for tracking grantor. Though, even without that, we track
the grantor of most other grants (possibly all currently?) and it seems
like a useful bit of information for DBAs to be able to know who granted
what to whom.
I can't say I've used it though, personally. Of course, I'll be pretty
unhappy if a day comes when I do need it and it's not there. :)
Thanks,
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Jose Blanco | 2007-05-04 19:43:35 | Re: order by question. |
Previous Message | Stephan Szabo | 2007-05-04 19:38:09 | Re: order by question. |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2007-05-04 20:18:28 | Re: Removing pg_auth_members.grantor (was Grantor name gets lost when grantor role dropped) |
Previous Message | jaba the mobzy | 2007-05-04 19:28:51 | Re: Bitmap Heap Scan anomaly |