Re: [GENERAL] reload postgresql with invalid pg_hba.conf - Mailing list pgsql-general

From Tom Lane
Subject Re: [GENERAL] reload postgresql with invalid pg_hba.conf
Date
Msg-id 25480.1505763360@sss.pgh.pa.us
Whole thread Raw
In response to [GENERAL] reload postgresql with invalid pg_hba.conf  (jotpe <jotpe@posteo.de>)
Responses Re: [GENERAL] reload postgresql with invalid pg_hba.conf  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-general
jotpe <jotpe@posteo.de> writes:
> A system administration applied an invalid line into the pg_hba.conf 
> file and called "service postgresql reload". Since that command doesn't 
> return any error and leaves with exit code 0 it seams that new 
> configuration was applied.

> Of course postgresql added a warning to the log file: "pg_hba.conf not 
> reloaded".
> But even when I execute SELECT pg_reload_conf(), true is returned.

> Is this the desired behavior?

I wouldn't say it's desired behavior, exactly, but there's no very
good way to improve it.  pg_ctl has no visibility into what the postmaster
is thinking.
        regards, tom lane


-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

pgsql-general by date:

Previous
From: jotpe
Date:
Subject: [GENERAL] reload postgresql with invalid pg_hba.conf
Next
From: Rafal Pietrak
Date:
Subject: Re: [GENERAL] looking for a globally unique row ID