pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Justin Pryzby <pryzby@telsasoft.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org
Cc: bruce@momjian.us
Cc: tgl@sss.pgh.pa.us
Subject: Re: GUC flags
Date: Tue, 25 Jan 2022 11:47:14 +0100
Message-ID: <d363c358-2c67-92bc-660f-ff82636c155f@enterprisedb.com> (raw)
In-Reply-To: <20220125010729.GC23027@telsasoft.com>
References: <YbG7sp+2YEYgbY0D@paquier.xyz>
	<20211209155322.GG17618@telsasoft.com>
	<20211229023240.GM24477@telsasoft.com>
	<20220105.114757.369416916044334409.horikyota.ntt@gmail.com>
	<20220105030648.GE14051@telsasoft.com>
	<YdUp118ekFgGiixT@paquier.xyz>
	<20220105235517.GR14051@telsasoft.com>
	<YdZ7zCymonPV4//X@paquier.xyz>
	<20220106053641.GW14051@telsasoft.com>
	<20220125010729.GC23027@telsasoft.com>

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.





view thread (44+ messages)  latest in thread

Message-ID: <d363c358-2c67-92bc-660f-ff82636c155f@enterprisedb.com>
Permalink:  ../d363c358-2c67-92bc-660f-ff82636c155f@enterprisedb.com/
Also on:    postgresql.org/message-id/d363c358-2c67-92bc-660f-ff82636c155f@enterprisedb.com

 · 

reply

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: peter.eisentraut@enterprisedb.com, pryzby@telsasoft.com, michael@paquier.xyz, horikyota.ntt@gmail.com, pgsql-hackers@lists.postgresql.org, bruce@momjian.us, tgl@sss.pgh.pa.us
  Subject: Re: GUC flags
  In-Reply-To: <d363c358-2c67-92bc-660f-ff82636c155f@enterprisedb.com>

* 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