From: Tom Lane <tgl@sss.pgh.pa.us>
To: =?UTF-8?Q?R=C4=B1dvan_Korkmaz?= <serkan.ridvan.korkmaz@gmail.com>
cc: pgsql-admin@postgresql.org
Subject: Re: pg_file_settings
In-reply-to: 
 <CAK30z9TLFenreqjg443JV-S88w=VajLMdmHqCMej6Eki5752pg@mail.gmail.com>
References: 
 <CAK30z9T9gaF_isNquccZxi7agXCSjPjMsFXiifmkfu4VpZguxw@mail.gmail.com>
 <CAK30z9TLFenreqjg443JV-S88w=VajLMdmHqCMej6Eki5752pg@mail.gmail.com>
Comments: In-reply-to =?UTF-8?Q?R=C4=B1dvan_Korkmaz?=
 <serkan.ridvan.korkmaz@gmail.com>
	message dated "Tue, 26 Dec 2023 21:12:24 +0300"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2091030.1703618573.1@sss.pgh.pa.us>
Date: Tue, 26 Dec 2023 14:22:53 -0500
Message-ID: <2091031.1703618573@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2091031.1703618573%40sss.pgh.pa.us>
Precedence: bulk

=?UTF-8?Q?R=C4=B1dvan_Korkmaz?= <serkan.ridvan.korkmaz@gmail.com> writes:
> In order to summarize things in first mail, from the documentation, we
> expect to see relevant errors in the "error" column of pg_file_setitings
> view for an invalid value of parameter.

Thanks for the report.  It mostly does work, but not for
'log_connections', and it turns out also not for other PGC_BACKEND
GUCs (of which there are only half a dozen, probably explaining how
this didn't get noticed).  I posted a proposed fix at [1].

			regards, tom lane

[1] https://www.postgresql.org/message-id/2089235.1703617353%40sss.pgh.pa.us