Horton

Re: Improve documentation regarding custom settings, placeholders, and the administrative functions

Zhang Mingli <zmlpostgres@gmail.com>

View thread View on postgr.es
From: Zhang Mingli <zmlpostgres@gmail.com>
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-02-28T01:32:49Z
Lists: pgsql-hackers 
On Feb 28, 2025 at 02:27 +0800, David G. Johnston <david.g.johnston@gmail.com>, wrote:
> 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.
Hi, Done.


--
Zhang Mingli
HashData

Commits

  1. docs: Clarify that NULL arg to set_config() means reset to default