Horton
Menu

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

Mark Dilger <mark.dilger@enterprisedb.com>

View thread
From: Mark Dilger <mark.dilger@enterprisedb.com>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: David Rowley <dgrowleyml@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, Joe Conway <mail@joeconway.com>, Alvaro Herrera <alvherre@alvh.no-ip.org>, PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Date: 2022-04-07T16:19:33Z
Lists: pgsql-hackers 

> On Apr 7, 2022, at 6:21 AM, Andrew Dunstan <andrew@dunslane.net> wrote:
> 
> \dconf seems fine to me

We have too many synonyms for configuration parameters.  "config", "guc", "parameter", and "setting" are already in use.  I thought we agreed on the other thread that "setting" means the value, and "parameter" is the thing being set.  It's true that "config" refers to parameters in the name of pg_catalog.set_config, which is a pretty strong precedent, but sadly "config" also refers to configuration files, the build configuration (as in the "pg_config" tool), text search configuration, etc.

While grep'ing through doc/src/sgml, I see no instances of "conf" ever referring to configuration parameters.  It only ever refers to configuration files.  I'd prefer not adding it to the list of synonyms.

—
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 →

  1. Be more careful about GucSource for internally-driven GUC settings.

  2. Fix case sensitivity in psql's tab completion for GUC names.

  3. Further tweak the default behavior of psql's \dconfig.

  4. Tweak the default behavior of psql's \dconfig.

  5. psql: add \dconfig command to show server's configuration parameters.

  6. Allow granting SET and ALTER SYSTEM privileges on GUC parameters.