public inbox for [email protected]
help / color / mirror / Atom feedpg_file_settings
2+ messages / 2 participants
[nested] [flat]
* pg_file_settings
@ 2023-12-25 11:37 Rıdvan Korkmaz <[email protected]>
2023-12-26 04:55 ` Re: pg_file_settings Aditya Toshniwal <[email protected]>
0 siblings, 1 reply; 2+ messages in thread
From: Rıdvan Korkmaz @ 2023-12-25 11:37 UTC (permalink / raw)
To: [email protected]
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]
Attachments:
[image/png] image.png (38.9K, 3-image.png)
download | view image
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: pg_file_settings
2023-12-25 11:37 pg_file_settings Rıdvan Korkmaz <[email protected]>
@ 2023-12-26 04:55 ` Aditya Toshniwal <[email protected]>
0 siblings, 0 replies; 2+ messages in thread
From: Aditya Toshniwal @ 2023-12-26 04:55 UTC (permalink / raw)
To: Rıdvan Korkmaz <[email protected]>; +Cc: [email protected]
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
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2023-12-26 04:55 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2023-12-25 11:37 pg_file_settings Rıdvan Korkmaz <[email protected]>
2023-12-26 04:55 ` Aditya Toshniwal <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox