From: | Rıdvan Korkmaz <serkan(dot)ridvan(dot)korkmaz(at)gmail(dot)com> |
---|---|
To: | pgadmin-hackers(at)lists(dot)postgresql(dot)org |
Subject: | pg_file_settings |
Date: | 2023-12-25 11:37:27 |
Message-ID: | CAK30z9TaZG5KnYrs8uBLoUo74i-eVasfHVmUenaj-LtooBrdiA@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
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]
From | Date | Subject | |
---|---|---|---|
Next Message | Aditya Toshniwal | 2023-12-26 04:55:45 | Re: pg_file_settings |
Previous Message | dependabot[bot] | 2023-12-25 10:42:41 | [pgadmin-org/pgadmin4] |