From: Pavel Luzanov <p.luzanov@postgrespro.ru>
To: Isaac Morland <isaac.morland@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Nathan Bossart <nathandbossart@gmail.com>
Cc: Justin Pryzby <pryzby@telsasoft.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: add \dpS to psql
Date: Thu, 8 Dec 2022 14:03:43 +0300
Message-ID: <1c031553-46d8-e1cd-4f64-caa349f111f9@postgrespro.ru> (raw)
In-Reply-To: <CAMsGm5drUvuH789D98Wo_bZggNhUn1LsBYuheJUbKaBsErtY9w@mail.gmail.com>
References: <20221206193606.GB3078082@nathanxps13>
<661148f4-c7f1-dec1-2bc8-29f3bd58e242@postgrespro.ru>
<20221208023929.GB27893@telsasoft.com>
<20221208041900.GB216874@nathanxps13>
<39743.1670473532@sss.pgh.pa.us>
<CAMsGm5drUvuH789D98Wo_bZggNhUn1LsBYuheJUbKaBsErtY9w@mail.gmail.com>
On 08.12.2022 07:48, Isaac Morland wrote:
> If we implement MAINTAIN to control access to VACUUM, ANALYZE,
> REFRESH, CLUSTER, and REINDEX, we will cover everything that I can
> find that has seriously discussed on this list
I like this approach with MAINTAIN privilege. I'm trying to find any
disadvantages ... and I can't.
For the complete picture, I tried to see what other actions with the
table could *potentially* be considered as maintenance.
Here is the list:
- create|alter|drop on extended statistics objects
- alter table|index alter column set statistics
- alter table|index [re]set (storage_parameters)
- alter table|index set tablespace
- alter table alter column set storage|compression
- any actions with the TOAST table that can be performed separately from
the main table
I have to admit that the discussion has moved away from the $subject.
--
Pavel Luzanov
Postgres Professional: https://postgrespro.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: p.luzanov@postgrespro.ru, isaac.morland@gmail.com, tgl@sss.pgh.pa.us, nathandbossart@gmail.com, pryzby@telsasoft.com
Subject: Re: add \dpS to psql
In-Reply-To: <1c031553-46d8-e1cd-4f64-caa349f111f9@postgrespro.ru>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox