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 1nCJMG-0005BZ-BQ for pgsql-hackers@arkaria.postgresql.org; Tue, 25 Jan 2022 10:47:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nCJME-0000eO-UZ for pgsql-hackers@arkaria.postgresql.org; Tue, 25 Jan 2022 10:47:26 +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 1nCJMD-0000eF-S5 for pgsql-hackers@lists.postgresql.org; Tue, 25 Jan 2022 10:47:26 +0000 Received: from wout2-smtp.messagingengine.com ([64.147.123.25]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nCJM8-0002jF-M9 for pgsql-hackers@lists.postgresql.org; Tue, 25 Jan 2022 10:47:25 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 318A43202210; Tue, 25 Jan 2022 05:47:17 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Tue, 25 Jan 2022 05:47:17 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=Dpzxrce/QuVMTmLgejeOZ1SMiJFuixRNFkV+pHgd5 Lw=; b=EEVkcCfXUjgqClwyBrQGyjK9hc2K2fNxlOzEXq/gfiiRBeMjNdF8+wXxW 0aay7P1Hj8hRk/DFhApi4VbSNK/7PWfHuU6ikeKKtgKoyleKDDpdohgZmvjDrbR1 4lsvI8iqgyPtpfV8dormkJcE+N08frVR0u0mMHlvfFPXZ4iXSr7ncfbK1KyAAqvY xmsfxeuxlikamSWS+j6RO9BlPsYCvBnd5+V3knXMMi5vCmmpd4QKGYpHKkRIWca7 QCO4bF7wEIk7r7rUVt5w2j9Ey3XBXAJqZGrdN7frqQoDzyy/vCN1uvTNtYbcVT7n kFLYFNuxh0Y8abHmWmE3CmFlbqcYg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrvdelgddukecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefkffggfgfuvfhfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvghtvghr ucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvghnthgvrh hprhhishgvuggsrdgtohhmqeenucggtffrrghtthgvrhhnpeefjeegheetuefhveevudel ueeftdejteeiffetvdduhfdtieefgfeutedtveeggfenucevlhhushhtvghrufhiiigvpe dtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvghnthhrrghuthes vghnthgvrhhprhhishgvuggsrdgtohhm X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 25 Jan 2022 05:47:14 -0500 (EST) Message-ID: Date: Tue, 25 Jan 2022 11:47:14 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: GUC flags Content-Language: en-US To: Justin Pryzby , Michael Paquier Cc: Kyotaro Horiguchi , pgsql-hackers@lists.postgresql.org, bruce@momjian.us, tgl@sss.pgh.pa.us References: <20211209155322.GG17618@telsasoft.com> <20211229023240.GM24477@telsasoft.com> <20220105.114757.369416916044334409.horikyota.ntt@gmail.com> <20220105030648.GE14051@telsasoft.com> <20220105235517.GR14051@telsasoft.com> <20220106053641.GW14051@telsasoft.com> <20220125010729.GC23027@telsasoft.com> From: Peter Eisentraut In-Reply-To: <20220125010729.GC23027@telsasoft.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 25.01.22 02:07, Justin Pryzby wrote: > +CREATE TABLE pg_settings_flags AS SELECT name, category, > + 'NO_SHOW_ALL' =ANY(flags) AS no_show_all, > + 'NO_RESET_ALL' =ANY(flags) AS no_reset_all, > + 'NOT_IN_SAMPLE' =ANY(flags) AS not_in_sample, > + 'EXPLAIN' =ANY(flags) AS guc_explain, > + 'COMPUTED' =ANY(flags) AS guc_computed > + FROM pg_show_all_settings(); Does this stuff have any value for users? I'm worried we are exposing a bunch of stuff that is really just for internal purposes. Like, what value does showing "not_in_sample" have? On the other hand, "guc_explain" might be genuinely useful, since that is part of a user-facing feature. (I don't like the "guc_*" naming though.) Your patch doesn't contain a documentation change, so I don't know how and to what extend this is supposed to be presented to users.