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

Mark Dilger <mark.dilger@enterprisedb.com>

From: Mark Dilger <mark.dilger@enterprisedb.com>

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

Cc: Tom Lane <tgl@sss.pgh.pa.us>, Joe Conway <mail@joeconway.com>, Alvaro Herrera <alvherre@alvh.no-ip.org>, pgsql-hackers@lists.postgresql.org

Date: 2022-04-06T22:36:08Z

Lists: pgsql-hackers

> On Apr 6, 2022, at 2:34 PM, Jonathan S. Katz <jkatz@postgresql.org> wrote:
> 
> "\sc" would make sense

I originally wrote the command as \dcp (describe configuration parameter) because \dp (describe parameter) wasn't available.  The thing we're showing is a "parameter", not a "config".  If we're going to use a single letter, I'd prefer /p/.

—
Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

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