| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Amir Rohan <amir(dot)rohan(at)zoho(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 21:14:19 |
| Message-ID: | 20151013211419.GW4405@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2015-10-13 21:28:24 | Re: Performance improvement for joins where outer side is unique |
| Previous Message | Amir Rohan | 2015-10-13 21:02:48 | Re: Proposal: pg_confcheck - syntactic & semantic validation of postgresql configuration files |