Re: BUG #16652: SELECT pg_reload_conf(); returning true despite loading config has failed - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: BUG #16652: SELECT pg_reload_conf(); returning true despite loading config has failed
Date
Msg-id CAKFQuwbofsP0MOQWEisfMM5=p6gwbLq-NULL67Xkw3vep_ygUg@mail.gmail.com
Whole thread Raw
In response to BUG #16652: SELECT pg_reload_conf(); returning true despite loading config has failed  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
On Saturday, October 3, 2020, PG Bug reporting form <noreply@postgresql.org> wrote:
The following bug has been logged on the website:

Bug reference:      16652
Logged by:          Christoph Gößmann
Email address:      mail@goessmann.io
PostgreSQL version: 11.4
Operating system:   CentOS Linux 7
Description:       

The command "SELECT pg_reload_conf();" returns TRUE, letting the admin
believe that the new configuration is active and that potentially new IP
rejects or other security modifications now are active (if performed at the
same opportunity) -- especially since users typically do not check the logs
regularly if there is no problem they are aware of.


The documentation could maybe better describe what is considered successful but these functions state they signal other, multiple, backends.  Signaling is unidirectional so practically speaking all the function knows is that it successfully sent the signals, not that those signals were received and/or successfully processed; information it doesn’t readily have.

David J.

pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #16652: SELECT pg_reload_conf(); returning true despite loading config has failed
Next
From: PG Bug reporting form
Date:
Subject: BUG #16653: Regression in CTE evaluation