"David G. Johnston" writes:
> On Mon, Sep 18, 2017 at 12:36 PM, Tom Lane wrote:
>> 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.
>
On Mon, Sep 18, 2017 at 12:36 PM, Tom Lane wrote:
> jotpe 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
jotpe 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
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: