Re: Improve documentation regarding custom settings, placeholders, and the administrative functions
David G. Johnston <david.g.johnston@gmail.com>
From: "David G. Johnston" <david.g.johnston@gmail.com>
To: Zhang Mingli <zmlpostgres@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-02-27T18:26:37Z
Lists: pgsql-hackers
On Thu, Feb 6, 2025 at 8:04 AM Zhang Mingli <zmlpostgres@gmail.com> wrote: > On Feb 6, 2025 at 10:49 +0800, David G. Johnston < > david.g.johnston@gmail.com>, wrote: > > > Yes, and when it does it is doing so in lieu of an error, and thus it is > not returning the value of the setting. It does not mean the value taken > on by the named parameter is NULL, which is not possible. i.e., SHOW will > never produce NULL. > > Hi, > > OK, LGTM. > > Thank you for the review. If you would like to add yourself as the reviewer and mark this ready to commit here is the commitfest entry. https://commitfest.postgresql.org/patch/5548/ David J.
Commits
-
docs: Clarify that NULL arg to set_config() means reset to default
- b4f453f6ab71 18.0 landed