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

From Andres Freund
Subject Re: Proposal: pg_confcheck - syntactic & semantic validation of postgresql configuration files
Date
Msg-id 1CC2BF77-0C93-412A-9FFD-F0BA602DA049@anarazel.de
Whole thread Raw
In response to Re: Proposal: pg_confcheck - syntactic & semantic validation of postgresql configuration files  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Proposal: pg_confcheck - syntactic & semantic validation of postgresql configuration files  (Amir Rohan <amir.rohan@zoho.com>)
List pgsql-hackers
On October 13, 2015 11:14:19 PM GMT+02:00, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
>Amir Rohan wrote:
>
>> I've been considering that. Reusing the parser would ensure no errors
>> are introduces by having a different implementation, but on the other
>> hand involving the pg build in installation what's intended as a
>> lightweight, independent tool would hurt.
>> Because it's dubious whether this will end up in core, I'd like
>> "pip install pg_confcheck" to be all that is required.
>
>Maybe just compile a single file in a separate FRONTEND environment?

Maybe I'm missing something here - but doesn't the posted binary do nearly all of this for you already? There's the
optionto display the value of a config option, and that checks the validity of the configuration. Might need to add an
optionto validate hba.conf et al as well and allow to display all values. That should be pretty simple?
 

--- 
Please excuse brevity and formatting - I am writing this on my mobile phone.



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Proposal: pg_confcheck - syntactic & semantic validation of postgresql configuration files
Next
From: Robbie Harwood
Date:
Subject: Re: [PATCH v3] GSSAPI encryption support