| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Parsing of pg_hba.conf and authentication inconsistencies |
| Date: | 2008-08-02 17:21:53 |
| Message-ID: | 489497B1.10105@commandprompt.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
>> Tom Lane wrote:
>>> Idle thought: maybe what would really make sense here is a "lint"
>>> for PG config files,
>
>> I like this idea.
>
>> postgres --check-hba-file /path/to/hba.conf
>> postgres --check-conf-file /path/to/postgresql.conf
>
>> (I think it's better to reuse the same postmaster executable, because
>> that way it's easier to have the same parsing routines.)
>
> I'd go for just
>
> postgres --check-config -D $PGDATA
>
> (In a reload scenario, you'd edit the files in-place and then do this
> before issuing SIGHUP.)
>
> regards, tom lane
Doesn't it seem reasonable that it should be pg_ctl? You should never
run postgres directly unless it is for DR.
Joshua D. Drake
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2008-08-02 17:27:43 | Re: Parsing of pg_hba.conf and authentication inconsistencies |
| Previous Message | Joshua D. Drake | 2008-08-02 17:20:22 | Re: Parsing of pg_hba.conf and authentication inconsistencies |