From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
---|---|
To: | Andres Freund <andres(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Thom Brown <thom(at)linux(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Incorrectly reporting config errors |
Date: | 2014-01-22 16:32:46 |
Message-ID: | 1390408366.2928.YahooMailNeo@web122304.mail.ne1.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> A rather common and sensible configuration is to have a common
> configuration file used across servers, which then is overwritten
> by a per-server or per-cluster config file containing values
> specific to a server/cluster.
Agreed.
My preference would be to not generate noise for interim states;
just report net changes. And don't say that a file "contains
errors" when we mean "those options are ignored on reload; they
will only take effect on restart".
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2014-01-22 16:35:39 | Re: Hard limit on WAL space used (because PANIC sucks) |
Previous Message | Andres Freund | 2014-01-22 16:21:15 | WAL replay should fdatasync() segments? |