From: Tom Lane <tgl@sss.pgh.pa.us>
To: RAJAMOHAN <garajamohan@gmail.com>
cc: pgsql-admin@lists.postgresql.org
Subject: Re: SELECT pg_reload_conf();
 returning true despite hba file loading was failed
In-reply-to: 
 <CAFzdntvG95eRKf0NByK4edmG8AWwLvn2-AE5R8UZiwQu=YCRqw@mail.gmail.com>
References: 
 <CAFzdntvG95eRKf0NByK4edmG8AWwLvn2-AE5R8UZiwQu=YCRqw@mail.gmail.com>
Comments: In-reply-to RAJAMOHAN <garajamohan@gmail.com>
	message dated "Fri, 05 Feb 2021 11:29:25 +0530"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <81340.1612505480.1@sss.pgh.pa.us>
Date: Fri, 05 Feb 2021 01:11:20 -0500
Message-ID: <81341.1612505480@sss.pgh.pa.us>
Precedence: bulk

RAJAMOHAN <garajamohan@gmail.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.)

> Is there any option to check if the load is successful or not, without
> going through the logs?

The pg_hba_file_rules view can help you debug a faulty pg_hba file.

			regards, tom lane