Re: Documentation clarification re: ANALYZE

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Isaac Morland <isaac(dot)morland(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Documentation clarification re: ANALYZE
Date: 2019-08-07 22:01:31
Message-ID: CAKFQuwakfxyYCJ+MVG5-B+Df0gO3giaZ=finF45r8+Apq4=fpw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Aug 7, 2019 at 2:42 PM Isaac Morland <isaac(dot)morland(at)gmail(dot)com>
wrote:

> Thanks. So presumably I would also have permission if I have SET ROLEd to
> the owner, or to a role which is an INHERIT member of the owner.
>

Yes, the table ownership role check walks up the role membership hierarchy
if "inherit" is on for the current role.

David J.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Sehrope Sarkuni 2019-08-07 23:40:05 Re: [Proposal] Table-level Transparent Data Encryption (TDE) and Key Management Service (KMS)
Previous Message Alexander Korotkov 2019-08-07 21:55:55 Re: SQL/JSON path: collation for comparisons, minor typos in docs