From: | Amir Rohan <amir(dot)rohan(at)zoho(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hacker mailing list <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Proposal: pg_confcheck - syntactic & semantic validation of postgresql configuration files |
Date: | 2015-10-13 22:54:46 |
Message-ID: | 561D8BB6.6050005@zoho.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 10/14/2015 01:16 AM, Andres Freund wrote:
> On October 13, 2015 11:14:19 PM GMT+02:00, Alvaro Herrera <alvherre(at)2ndquadrant(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Noah Misch | 2015-10-14 01:08:52 | Re: Parallel Seq Scan |
Previous Message | Amir Rohan | 2015-10-13 22:52:21 | Re: Proposal: pg_confcheck - syntactic & semantic validation of postgresql configuration files |