I looked at the psql manpage and the HTML rendering of section 5.6 and
it all looks good to me.
Indeed, this looks great, a precise and full description of privileges
just in one place.
Pushed (with a little bit more tweaking).
Thanks for the rewrite, extensions, improvements and final p
Fabien COELHO writes:
>>> I feel if we're going to do anything, we should put a unified description
>>> of privileges and aclitem-reading into section 5.6, and take that material
>>> out of the various places where it lives now. Like the attached, in which
>>> I failed to resist the temptation to
I feel if we're going to do anything, we should put a unified description
of privileges and aclitem-reading into section 5.6, and take that material
out of the various places where it lives now. Like the attached, in which
I failed to resist the temptation to wordsmith some stuff as well as m
On 2018-Nov-30, Tom Lane wrote:
> I feel if we're going to do anything, we should put a unified description
> of privileges and aclitem-reading into section 5.6, and take that material
> out of the various places where it lives now. Like the attached, in which
> I failed to resist the temptation
Fabien COELHO writes:
> Attached v4:
> - moves the table to the privileges section
> - updates the table column headers
> - adds a privilege/aclitem letter mapping table
> - adds some appropriate links towards psql & aclitem
TBH, I don't think this goes nearly far enough. It seems like i
Hello Tom,
Thanks for this precise feedback.
Progress on this patch seems to be blocked on the question of whether
we want to keep enlarging the amount of psql-specific information
in the GRANT reference page, or move that all somewhere else.
Yep.
FWIW, I think I agree with Peter's positio
Progress on this patch seems to be blocked on the question of whether
we want to keep enlarging the amount of psql-specific information
in the GRANT reference page, or move that all somewhere else.
FWIW, I think I agree with Peter's position that moving it somewhere
else is the better option. Sec
On Fri, Sep 28, 2018 at 04:15:13PM -0300, Alvaro Herrera wrote:
> There is a legitimate point in doing this, though, since the GRANT page
> is already explaining how does psql display privileges. Maybe the right
> solution is move that stuff all to the psql documentation, and alter the
> GRANT pag
The Owner column is redundant, because it's always all applicable
privileges. (Having this column would give the impression that it's not
always all privileges, so it would be confusing.)
The reason I put the owner column is to show (1) the privileges that apply
to the objects (i.e. what is
On 2018-Sep-28, Peter Eisentraut wrote:
> The psql commands seem out of place here. If you want to learn about
> how to use psql, you can go to the psql documentation.
There is a legitimate point in doing this, though, since the GRANT page
is already explaining how does psql display privileges.
Some thoughts:
We should keep the GRANT reference page about GRANT. There is a section
about Privileges in the Data Definition chapter, which we could use to
expand on general concepts.
The ALTER DEFAULT PRIVILEGES reference page would be another place this
could be put.
The Owner column is red
I have not found a convenient presentation of the default privileges for
different objects, and how to display them (if possible, not always).
The information is partly provided within the GRANT description, and not very
explicit: eg it is said that owners have all possible perms, but which t
12 matches
Mail list logo
