Re: How about a psql backslash command to show GUCs?
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Pavel Stehule <pavel.stehule@gmail.com>
Cc: "David G. Johnston" <david.g.johnston@gmail.com>,
Joe Conway <mail@joeconway.com>,
Mark Dilger <mark.dilger@enterprisedb.com>,
Andrew Dunstan <andrew@dunslane.net>,
David Rowley <dgrowleyml@gmail.com>,
Alvaro Herrera <alvherre@alvh.no-ip.org>,
PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Date: 2022-04-07T20:35:59Z
Lists: pgsql-hackers
Pavel Stehule <pavel.stehule@gmail.com> writes: > čt 7. 4. 2022 v 19:04 odesílatel David G. Johnston < > david.g.johnston@gmail.com> napsal: >> \dconfig[+] gets my vote. I was going to say "conf" just isn't common >> jargon to say or write; but the one place it is - file extensions - is >> relevant and common. But still, I would go with the non-jargon form. > dconfig is better, because google can be confused - dconf is known project > https://en.wikipedia.org/wiki/Dconf Looks like the consensus has shifted to \dconfig. I'll do it like that. regards, tom lane
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