Re: Role membership and DROP

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
Cc: pgsql-hackers(at)postgresql(dot)org, pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: Role membership and DROP
Date: 2019-11-19 18:21:37
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-docs pgsql-hackers

Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> writes:
> On Fri, 2019-11-15 at 13:41 -0500, Tom Lane wrote:
>> Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> writes:
>>> On Wed, 2019-11-13 at 17:17 -0500, Tom Lane wrote:
>>>> It might be worth clarifying this point in section 5.7,

> I like your second sentence, but I think that "the right ... is inherent
> in being the ... owner" is unnecessarily complicated.
> Removing the "always" and "only" makes the apparent contradiction between
> the sentences less jarring to me.

I think it's important to emphasize that this is implicit in object

Looking at the page again, I notice that there's a para a little further
down that overlaps quite a bit with what we're discussing here, but it's
about implicit grant options rather than the right to DROP. In the
attached, I reworded that too, and moved it because it's not fully
intelligible until we've explained grant options. Thoughts?

regards, tom lane

Attachment Content-Type Size
doc-owner-privileges-3.patch text/x-diff 1.7 KB

In response to


Browse pgsql-docs by date

  From Date Subject
Next Message PG Doc comments form 2019-11-19 18:55:23 Difference between Bulk Load (Multiple inserts or single inserts) and COPY
Previous Message Tom Lane 2019-11-19 15:58:13 Re: GSoD - a patch for Getting Started tutorial

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2019-11-19 18:58:16 Re: logical decoding : exceeded maxAllocatedDescs for .spill files
Previous Message Tom Lane 2019-11-19 17:06:50 Re: initdb SegFault