On Wed, Aug 07, 2019 at 05:54:14PM -0400, Tom Lane wrote:
> Actually, looking in the source code finds
>
> * We allow the user to vacuum or analyze a table if he is superuser, the
> * table owner, or the database owner (but in the latter case, only if
> * it's not a shared
On Wed, Aug 7, 2019 at 2:42 PM Isaac Morland
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
"David G. Johnston" writes:
> On Wed, Aug 7, 2019 at 2:14 PM Isaac Morland
> wrote:
>> I'm looking at https://www.postgresql.org/docs/current/sql-analyze.html,
>> where it says “Without a table_and_columns list, ANALYZE processes every
>> table and materialized view in the current database that
On Wed, 7 Aug 2019 at 17:31, David G. Johnston
wrote:
> On Wed, Aug 7, 2019 at 2:14 PM Isaac Morland
> wrote:
>
>> I'm looking at https://www.postgresql.org/docs/current/sql-analyze.html,
>> where it says “Without a table_and_columns list, ANALYZE processes every
>> table and materialized view
On Wed, Aug 7, 2019 at 2:14 PM Isaac Morland
wrote:
> I'm looking at https://www.postgresql.org/docs/current/sql-analyze.html,
> where it says “Without a table_and_columns list, ANALYZE processes every
> table and materialized view in the current database that the current user
> has permission
I'm looking at https://www.postgresql.org/docs/current/sql-analyze.html,
where it says “Without a table_and_columns list, ANALYZE processes every
table and materialized view in the current database that the current user
has permission to analyze.”.
I don’t believe there is a separate “analyze”
