| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | RAJAMOHAN <garajamohan(at)gmail(dot)com>, "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: SELECT pg_reload_conf(); returning true despite hba file loading was failed |
| Date: | 2021-02-05 06:32:49 |
| Message-ID: | CAKFQuwZHNHht_D+PSx8NdUKeT6EJOjvk0gx0ZjCC+g_n+3JX6Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | RAJAMOHAN | 2021-02-05 06:40:06 | Re: SELECT pg_reload_conf(); returning true despite hba file loading was failed |
| Previous Message | Tom Lane | 2021-02-05 06:11:20 | Re: SELECT pg_reload_conf(); returning true despite hba file loading was failed |