On 10/14/2015 01:16 AM, Andres Freund wrote: > On October 13, 2015 11:14:19 PM GMT+02:00, Alvaro Herrera > <alvhe...@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 option to display the value of a > config option, and that checks the validity of the configuration. Might need > to add an option to validate hba.conf et al as well and allow to display all > values. That should be pretty simple? >
Andres, please see upthread for quite a bit on what it doesn't do, and why having it in the server is both an advantages and a shortcoming. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
