Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1p3Egu-0004mZ-EA for pgsql-hackers@arkaria.postgresql.org; Thu, 08 Dec 2022 11:03:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1p3Egt-0000Q7-AN for pgsql-hackers@arkaria.postgresql.org; Thu, 08 Dec 2022 11:03:47 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1p3Egs-0000Pm-Pz for pgsql-hackers@lists.postgresql.org; Thu, 08 Dec 2022 11:03:47 +0000 Received: from mail.postgrespro.ru ([93.174.131.139]) by magus.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1p3Egr-000071-3N for pgsql-hackers@postgresql.org; Thu, 08 Dec 2022 11:03:46 +0000 Received: from [192.168.0.104] (unknown [62.217.188.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mail.postgrespro.ru (Postfix) with ESMTPSA id 6B73B21C2461; Thu, 8 Dec 2022 14:03:43 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mail; t=1670497423; bh=wfDIPRhRZLaWnOTCPSaYor4HiwsTEAKjjeCACWwryPg=; h=Date:Subject:To:Cc:References:From:In-Reply-To; b=fqRvmmnAKdnqNNZuZHyF4srjxScRjwTDbzkY6/Tbyw4z62qf4sFBzwZAMzI8RLa/j sJMoH8rBDyiAZ1L2vJUefhl5CuEXHxX/nEbpF0z0QRpDXz7bcxczf8sgibW6TKcKX6 uMlTfAxIMBgIDK4S9dwp6ppOgklvENhUiznf03+Q= Message-ID: <1c031553-46d8-e1cd-4f64-caa349f111f9@postgrespro.ru> Date: Thu, 8 Dec 2022 14:03:43 +0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Subject: Re: add \dpS to psql Content-Language: en-US To: Isaac Morland , Tom Lane Cc: Nathan Bossart , Justin Pryzby , pgsql-hackers@postgresql.org References: <20221206193606.GB3078082@nathanxps13> <661148f4-c7f1-dec1-2bc8-29f3bd58e242@postgrespro.ru> <20221208023929.GB27893@telsasoft.com> <20221208041900.GB216874@nathanxps13> <39743.1670473532@sss.pgh.pa.us> From: Pavel Luzanov In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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