Re[2]: doc - improve description of default privileges

From: "Bradley DeJong" <bpd0018(at)gmail(dot)com>
To: "Fabien COELHO" <coelho(at)cri(dot)ensmp(dot)fr>, "PostgreSQL Developers" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re[2]: doc - improve description of default privileges
Date: 2018-08-27 22:19:49
Message-ID: emad457c23-d50a-4064-9bb0-891f429bde0a@dolphin
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Hi Fabien,

Thanks for writing this up - in particular the psql backslash commands.

comments on the patch ...

1) I think that adding the "This privilege is abbreviated ... when
displayed." lines to the privilege descriptions is redundant. The
abbreviations are already listed after the "The entries shown by \dp are
interpreted thus:" line. Just change that line to something like "The
entries shown by the psql backslash commands, like \dp, are interpreted

2) I think that the psql command table should go with the current text
on "Use psql's \dp command to obtain ..." rather than in the Examples
section. It seems like changing the "For non-table objects there are
other \d commands ..." line to an introductory comment like "The
following table lists the \d commands that are used for non-table
objects along with the default privileges granted to the object's owner

3) The table title, "Default hardcoded access privileges per object's
type", seems incomplete because it does not mention the psql commands
part of the table.

------ Original Message ------
From: "Fabien COELHO" <coelho(at)cri(dot)ensmp(dot)fr>
To: "PostgreSQL Developers" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Sent: 8/4/2018 4:40:33 AM
Subject: Re: doc - improve description of default privileges

>>I have not found a convenient presentation of the default privileges
>>for different objects, and how to display them (if possible, not
>>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 they are is not said explicitely, although they are implied
>>by the different GRANT sysnopsys. Then some objects are given perms
>>for the PUBLIC.
>>The attached patch tries to improve the documentation, in particular
>>with an added table to summarizes my findings, so that they are
>>recorded somewhere.
>The attached fixes the tablespace entry that I forgot to fill in full.
>-- Fabien.

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2018-08-28 00:36:50 Re: simplehash.h comment
Previous Message Jonathan S. Katz 2018-08-27 22:05:16 Re: FailedAssertion on partprune