| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Amir Rohan <amir(dot)rohan(at)zoho(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, 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-14 10:30:13 |
| Message-ID: | 20151014103013.GN10323@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2015-10-14 01:54:46 +0300, Amir Rohan wrote:
> 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.
As far as I have skimmed the thread it's only talking about shortcoming
in case it requires a running server. Which -C doesn't.
I don't think there's any fundamental difference between some external
binary parsing & validating the config file and the postgres binary
doing it. There *is* the question of the utility being able to to
process options from multiple major releases, but I don't think that's a
particularly worthwhile goal here.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Victor Wagner | 2015-10-14 10:41:51 | Patch: Implement failover on libpq connect level. |
| Previous Message | Andres Freund | 2015-10-14 10:14:36 | Re: remaining open items |