Re: SELECT pg_reload_conf(); returning true despite hba file loading was failed - Mailing list pgsql-admin

From RAJAMOHAN
Subject Re: SELECT pg_reload_conf(); returning true despite hba file loading was failed
Date
Msg-id CAFzdnttVeygMopGd21K2Tme9ofAiaZWkHYcninGCaiNOLQQMHQ@mail.gmail.com
Whole thread Raw
In response to Re: SELECT pg_reload_conf(); returning true despite hba file loading was failed  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-admin
Thanks Tom.

pg_hba_file_rules view will be helpful.


Thanks & Regards,
Rajamohan.J
Oracle DBA / Postgresql DBA
Mobile : +91 8098167651, +91 7259157485


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

On Thursday, February 4, 2021, Tom Lane <tgl@sss.pgh.pa.us> wrote:
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.)

My and Heikki’s recent changes to address this are only in head, not v13 or earlier.

David J. 

pgsql-admin by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: SELECT pg_reload_conf(); returning true despite hba file loading was failed
Next
From: Mai Peng
Date:
Subject: Re: Design database