Re: SELECT pg_reload_conf(); returning true despite hba file loading was failed

Thanks Tom.

pg_hba_file_rules view will be helpful.

Thanks & Regards,
Rajamohan.J
Oracle DBA / Postgresql DBA
Mobile : +91 8098167651, +91 7259157485
Email:garajamohan(at)gmail(dot)com

On Fri, Feb 5, 2021 at 12:02 PM David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:

>
> On Thursday, February 4, 2021, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
>> RAJAMOHAN <garajamohan(at)gmail(dot)com> writes:
>> > After checking the logs, I found out that the hba file was not loaded
>> > successfully because of the invalid character. My concern is
>> > why pg_reload_conf is returning true if the load was unsuccessful.
>>
>> A true result only indicates that a SIGHUP signal was sent to the
>> postmaster; your backend process has no visibility into whether the
>> signal was even received, never mind whether the postmaster did
>> what you wanted. (I thought this was adequately documented, but it
>> seems not.)
>>
>
> My and Heikki’s recent changes to address this are only in head, not v13
> or earlier.
>
> David J.
>