public inbox for [email protected]  

help / color / mirror / Atom feed

From: David Rowley <[email protected]>
To: Tom Lane <[email protected]>
Cc: Joe Conway <[email protected]>
Cc: Alvaro Herrera <[email protected]>
Cc: PostgreSQL Developers <[email protected]>
Cc: Mark Dilger <[email protected]>
Subject: Re: How about a psql backslash command to show GUCs?
Date: Thu, 7 Apr 2022 15:25:06 +1200
Message-ID: <CAApHDvoCyxBZqdvwc93cnsr_48zBY7wwYmZHhCjhgp-naiDKSA@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>

I also find myself querying pg_settings all too often. More typing
than I'd like.

On Thu, 7 Apr 2022 at 06:40, Tom Lane <[email protected]> wrote:
> I do agree that \show might be a bad choice, the reason being that
> the adjacent \set command is for psql variables not GUCs; if we
> had a \show I'd sort of expect it to be a variant spelling of
> "\echo :variable".

I also think \show is not a great choice. I'd rather see us follow the
\d pattern for showing information about objects in the database.

> "\sc" isn't awful perhaps.

I think \dG is pretty good. G for GUC.

David

view thread (7+ messages)

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]
  Subject: Re: How about a psql backslash command to show GUCs?
  In-Reply-To: <CAApHDvoCyxBZqdvwc93cnsr_48zBY7wwYmZHhCjhgp-naiDKSA@mail.gmail.com>

* 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