Re: Proposal: pg_confcheck - syntactic & semantic validation of postgresql configuration files
От | Alvaro Herrera |
---|---|
Тема | Re: Proposal: pg_confcheck - syntactic & semantic validation of postgresql configuration files |
Дата | |
Msg-id | 20151013221219.GX4405@alvherre.pgsql обсуждение исходный текст |
Ответ на | Re: Proposal: pg_confcheck - syntactic & semantic validation of postgresql configuration files (Amir Rohan <amir.rohan@zoho.com>) |
Ответы |
Re: Proposal: pg_confcheck - syntactic & semantic
validation of postgresql configuration files
|
Список | pgsql-hackers |
Amir Rohan wrote: > On 10/14/2015 12:14 AM, Alvaro Herrera 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? > > You mean refactoring the postgres like rhass means? could you elaborate? > > I believe most people get pg as provided by their distro or PaaS, > and not by compiling it. I mean the utility would be built by using a file from the backend source, just like pg_xlogdump does. We have several such cases. I don't think this is impossible to do outside core, either. -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: