Re: Incorrectly reporting config errors - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: Incorrectly reporting config errors
Date
Msg-id 1390408366.2928.YahooMailNeo@web122304.mail.ne1.yahoo.com
Whole thread Raw
In response to Re: Incorrectly reporting config errors  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: Incorrectly reporting config errors  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Andres Freund <andres@2ndquadrant.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



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: WAL replay should fdatasync() segments?
Next
From: Tom Lane
Date:
Subject: Re: Hard limit on WAL space used (because PANIC sucks)