mirror of
https://github.com/postgres/postgres.git
synced 2025-06-29 10:41:53 +03:00
psql: add \dconfig command to show server's configuration parameters.
Plain \dconfig is basically equivalent to SHOW except that you can give it a pattern with wildcards, either to match multiple GUCs or because you don't exactly remember the name you want. \dconfig+ adds type, context, and access-privilege information, mainly because every other kind of object privilege has a psql command to show it, so GUC privileges should too. (A form of this command was in some versions of the patch series leading up to commita0ffa885e
. We pulled it out then because of doubts that the design and code were up to snuff, but I think subsequent work has resolved that.) In passing, fix incorrect completion of GUC names in GRANT/REVOKE ON PARAMETER:a0ffa885e
neglected to use the VERBATIM form of COMPLETE_WITH_QUERY, so it misbehaved for custom (qualified) GUC names. Mark Dilger and Tom Lane Discussion: https://postgr.es/m/3118455.1649267333@sss.pgh.pa.us
This commit is contained in:
@ -918,8 +918,12 @@ processSQLNamePattern(PGconn *conn, PQExpBuffer buf, const char *pattern,
|
||||
* Convert shell-style 'pattern' into the regular expression(s) we want to
|
||||
* execute. Quoting/escaping into SQL literal format will be done below
|
||||
* using appendStringLiteralConn().
|
||||
*
|
||||
* If the caller provided a schemavar, we want to split the pattern on
|
||||
* ".", otherwise not.
|
||||
*/
|
||||
patternToSQLRegex(PQclientEncoding(conn), NULL, &schemabuf, &namebuf,
|
||||
patternToSQLRegex(PQclientEncoding(conn), NULL,
|
||||
(schemavar ? &schemabuf : NULL), &namebuf,
|
||||
pattern, force_escape);
|
||||
|
||||
/*
|
||||
|
Reference in New Issue
Block a user