From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
---|---|
To: | Kris Jurka <books(at)ejurka(dot)com> |
Cc: | Edgar Mares <edgarmaf(at)ife(dot)org(dot)mx>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: grants |
Date: | 2004-03-10 16:43:15 |
Message-ID: | 404F45A3.5050802@pse-consulting.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Kris Jurka wrote:
>On Wed, 10 Mar 2004, Andreas Pflug wrote:
>
>
>
>>Edgar Mares wrote:
>>
>>
>>
>>>hi there i'm having troubles to find how to
>>>GRANT SELECT ON all-tables-onmydb TO specificuser
>>>
>>>this is just to give the access to "specificuser" to query the
>>>database and find troubles on it
>>>
>>>
>>pgAdmin II has a tool for that (Security wizard; pgAdmin III has it on
>>the todo-list)
>>
>>
>>
>
>The problem that cannot be solved with either this or a function that
>loops and grants on each table is that it is not a permanent grant of what
>the admin had in mind. If a new table is added or an existing table is
>dropped and recreated, the grants must be done again. The real use of a
>SELECT ANY TABLE permission is ignorance of schema updates.
>
>
Hm, does this exist in other DBMS?
As soon as roles are implemented, there might be a default role
('public') for this. Until then, using groups solves most of the
problems (well, you certainly still need to GRANT rights to your
preferred group).
Regards,
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-03-10 16:43:48 | Re: Timing of 'SELECT 1' |
Previous Message | scott.marlowe | 2004-03-10 16:43:10 | Re: About hierarchical_query of Oracle |