Re: Proposal: pg_confcheck - syntactic & semantic validation of postgresql configuration files - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Proposal: pg_confcheck - syntactic & semantic validation of postgresql configuration files
Date
Msg-id 2942.1444304331@sss.pgh.pa.us
Whole thread Raw
In response to Proposal: pg_confcheck - syntactic & semantic validation of postgresql configuration files  (Amir Rohan <amir.rohan@zoho.com>)
Responses Re: Proposal: pg_confcheck - syntactic & semantic validation of postgresql configuration files  (Amir Rohan <amir.rohan@zoho.com>)
List pgsql-hackers
Amir Rohan <amir.rohan@zoho.com> writes:
> Comments?

ISTM that all of the "functional" parts of this are superseded by
pg_file_settings; or at least, if they aren't, you need to provide a
rationale that doesn't consist only of pointing to pre-9.5 discussions.
The "advice" parts of it maybe are still useful, but a tool that's just
meant for that would look quite a bit different.  Maybe what you're really
after is to update pgtune.

Also, as a general comment, the sketch you provided seems to require
porting everything the server knows about GUC file syntax, file locations,
variable names and values into some other representation that apparently
is not C, nor Perl either.  I think that's likely to be impossible to keep
accurate or up to date.  Just as a thought experiment, ask yourself how
you'd validate the TimeZone setting in external code, bearing in mind that
anytime you don't give exactly the same answer the server would, your tool
has failed to be helpful.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Андрей Асякин
Date:
Subject: Process pg_hba.conf keywords as case-insensitive
Next
From: Pavel Raiskup
Date:
Subject: Re: check fails on Fedora 23