Peter Eisentraut <[EMAIL PROTECTED]> 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
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
