Re: reload postgresql with invalid pg_hba.conf

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: jotpe <jotpe(at)posteo(dot)de>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: reload postgresql with invalid pg_hba.conf
Date: 2017-09-18 19:36:00
Message-ID: 25480.1505763360@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

jotpe <jotpe(at)posteo(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Rafal Pietrak 2017-09-18 19:59:08 Re: looking for a globally unique row ID
Previous Message jotpe 2017-09-18 19:27:12 reload postgresql with invalid pg_hba.conf