public inbox for [email protected]  
help / color / mirror / Atom feed
From: Aditya Toshniwal <[email protected]>
To: Rıdvan Korkmaz <[email protected]>
Cc: [email protected]
Subject: Re: pg_file_settings
Date: Tue, 26 Dec 2023 10:25:45 +0530
Message-ID: <CAM9w-_=wNQjNXU1rFDy1fBtxLNR9_5+M=C1Rf86NT1a9dww=gA@mail.gmail.com> (raw)
In-Reply-To: <CAK30z9TaZG5KnYrs8uBLoUo74i-eVasfHVmUenaj-LtooBrdiA@mail.gmail.com>
References: <CAK30z9TaZG5KnYrs8uBLoUo74i-eVasfHVmUenaj-LtooBrdiA@mail.gmail.com>

Hi Rıdvan,

This is a pgAdmin mailing list. Please send this to
[email protected] for PostgreSQL related questions.

On Mon, Dec 25, 2023 at 5:07 PM Rıdvan Korkmaz <
[email protected]> wrote:

> Hi,
> When I read the docs for pg_file_settings view on pg_file_settings
> <https://www.postgresql.org/docs/current/view-pg-file-settings.html;
>
> .... This view is helpful for checking whether planned changes in the
> configuration files will work, or for diagnosing a previous failure. Note
> that this view reports on the current contents of the files, not on what
> was last applied by the server. (The pg_settings view is usually sufficient
> to determine that.)
>
> But the following test shows the opposite. When the parameter value is
> "on" for *log_connections, *there is *no error for value*, which is the
> expected case. But If I change the value in postgresql.conf to *"dummy"*
> then re-run the query, this time *I expected the error column to show
> error*,* but again it is null, *which means, I potentially apply this
> value to the parameter.
>
> Is there something I am missing?
>
> Client and server is 16.1 from the RPM package.
>
> [image: image.png]
>
>

-- 
Thanks,
Aditya Toshniwal
pgAdmin Hacker | Sr. Software Architect | *enterprisedb.com*
<https://www.enterprisedb.com/;
"Don't Complain about Heat, Plant a TREE"


Attachments:

  [image/png] image.png (38.9K, 3-image.png)
  download | view image

view thread (2+ messages)

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: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: pg_file_settings
  In-Reply-To: <CAM9w-_=wNQjNXU1rFDy1fBtxLNR9_5+M=C1Rf86NT1a9dww=gA@mail.gmail.com>

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

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