Re: How about a psql backslash command to show GUCs?

Jonathan S. Katz <jkatz@postgresql.org>

From: "Jonathan S. Katz" <jkatz@postgresql.org>

To: "David G. Johnston" <david.g.johnston@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>

Cc: Joe Conway <mail@joeconway.com>, Alvaro Herrera <alvherre@alvh.no-ip.org>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Mark Dilger <mark.dilger@enterprisedb.com>

Date: 2022-04-07T01:27:23Z

Lists: pgsql-hackers

On 4/6/22 9:18 PM, David G. Johnston wrote:
> On Wed, Apr 6, 2022 at 6:16 PM Tom Lane <tgl@sss.pgh.pa.us 

>     I agree that \d-something makes the most sense from a functionality
>     standpoint.  But I don't want to make the name too long, even if we
>     do have tab completion to help.
> 
>     \dconf maybe?
> 
> 
> I don't have a strong preference, but just tossing it out there; maybe 
> embrace the novelty of GUC?
> 
> \dguc

+1 for \dconf

Jonathan

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Be more careful about GucSource for internally-driven GUC settings.
- 7ab5b4eb4834 15.0 landed
Fix case sensitivity in psql's tab completion for GUC names.
- b5607b0746f4 15.0 landed
Further tweak the default behavior of psql's \dconfig.
- 139d46ee26a2 15.0 landed
Tweak the default behavior of psql's \dconfig.
- 5e70d8b5d18b 15.0 landed
psql: add \dconfig command to show server's configuration parameters.
- 3e707fbb4009 15.0 landed
Allow granting SET and ALTER SYSTEM privileges on GUC parameters.
- a0ffa885e478 15.0 cited