pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Rıdvan Korkmaz <serkan.ridvan.korkmaz@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: pg_file_settings
Date: Tue, 26 Dec 2023 14:22:53 -0500
Message-ID: <2091031.1703618573@sss.pgh.pa.us> (raw)
In-Reply-To: <CAK30z9TLFenreqjg443JV-S88w=VajLMdmHqCMej6Eki5752pg@mail.gmail.com>
References: <CAK30z9T9gaF_isNquccZxi7agXCSjPjMsFXiifmkfu4VpZguxw@mail.gmail.com>
	<CAK30z9TLFenreqjg443JV-S88w=VajLMdmHqCMej6Eki5752pg@mail.gmail.com>

=?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

view thread (3+ messages)

Message-ID: <2091031.1703618573@sss.pgh.pa.us>
Permalink:  ../2091031.1703618573@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/2091031.1703618573@sss.pgh.pa.us

copy link · copy postgr.es

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, serkan.ridvan.korkmaz@gmail.com
  Subject: Re: pg_file_settings
  In-Reply-To: <2091031.1703618573@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox