| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, "korry" <korryd(at)enterprisedb(dot)com>, "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Magnus Hagander" <magnus(at)hagander(dot)net>, "Josh Berkus" <josh(at)agliodbs(dot)com>, "Gregory Stark" <stark(at)enterprisedb(dot)com> |
| Subject: | Re: Parsing of pg_hba.conf and authenticationinconsistencies |
| Date: | 2008-08-06 16:59:54 |
| Message-ID: | 15576.1218041994@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Am Tuesday, 5. August 2008 schrieb korry:
>> Perhaps the --check-config option should take an (optional) file name?
>> That would allow you to validate a config file without having to copy
>> it into place first.
>>
>> postgres --check-config=myFilenameGoesHere -D $PGDATA
> There is already an elaborate system to tell where configuration files are
> located. So just doing postgres --check-config -D myFilenameGoesHere should
> do the job.
Even more to the point: in the presence of include directives with
relative file paths, the idea of checking a file that's not in its
intended place is broken to begin with. Both pg_hba.conf and
postgresql.conf have include-type syntax, though the former doesn't
call it that.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2008-08-06 18:13:58 | Re: plan invalidation vs stored procedures |
| Previous Message | Hiroshi Saito | 2008-08-06 16:45:04 | Re: unable to build libpq on Win 2003 (32 bit) |