Re: [HACKERS] [PATCH] Warn users about duplicate configuration parameters - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: [HACKERS] [PATCH] Warn users about duplicate configuration parameters
Date
Msg-id CAKFQuwZzgE2BjQ0tqjOCwTpetnJsg_Um2rvCgw813+4FqEK6Cg@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] [PATCH] Warn users about duplicate configurationparameters  (Aleksander Alekseev <a.alekseev@postgrespro.ru>)
List pgsql-hackers
On Fri, Apr 7, 2017 at 8:29 AM, Aleksander Alekseev <a.alekseev@postgrespro.ru> wrote:
Andres, Tatsuo,

Thank you for sharing your thoughts.

> -1 - I frequently just override earlier parameters by adding an
> include at the end of the file.  Also, with postgresql.auto.conf it's
> even more common to override parameters.

> -1 from me too by the same reason Andres said.

I see no problem here. After all, it's just warnings. We can even add
a GUC that disables them specially for experienced users who knows what
she or he is doing. And/or add special case for postgresql.auto.conf.


​-1 for learning how the configuration system work via warning messages.

We've recently added pg_file_settings to provide a holistic view and the docs cover the topic quite well.

David J.

pgsql-hackers by date:

Previous
From: Euler Taveira
Date:
Subject: Re: [HACKERS] [PATCH] Warn users about duplicate configuration parameters
Next
From: Yorick Peterse
Date:
Subject: Re: [HACKERS] [PATCH] Document the order of changing certain settingswhen using hot-standby servers