public inbox for [email protected]  

help / color / mirror / Atom feed

From: Kyotaro Horiguchi <[email protected]>
To: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Subject: Re: GUC flags
Date: Wed, 05 Jan 2022 11:47:57 +0900 (JST)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>

At Tue, 28 Dec 2021 20:32:40 -0600, Justin Pryzby <[email protected]> wrote in 
> On Thu, Dec 09, 2021 at 09:53:23AM -0600, Justin Pryzby wrote:
> > On Thu, Dec 09, 2021 at 05:17:54PM +0900, Michael Paquier wrote:
> > One option is to expose the GUC flags in pg_settings, so this can all be done
> > in SQL regression tests.
> > 
> > Maybe the flags should be text strings, so it's a nicer user-facing interface.
> > But then the field would be pretty wide, even though we're only adding it for
> > regression tests.  The only other alternative I can think of is to make a
> > sql-callable function like pg_get_guc_flags(text guc).
> 
> Rebased on cab5b9ab2c066ba904f13de2681872dcda31e207.
> 
> And added 0003, which changes to instead exposes the flags as a function, to
> avoid changing pg_settings and exposing internally-defined integer flags in
> that somewhat prominent view.

Just an idea but couldn't we use flags in a series of one-letter flag
representations?  It is more user-friendly than integers but shorter
than full-text representation.

+SELECT name, flags FROM pg_settings;
          name          |  flags             
------------------------+--------
 application_name       |  ARsec
 transaction_deferrable |  Arsec
 transaction_isolation  |  Arsec
 transaction_read_only  |  Arsec

regards.

-- 
Kyotaro Horiguchi
NTT Open Source Software Center

view thread (3+ messages)  latest in thread

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: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: GUC flags
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox