| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
| Subject: | Re: [PATCH] Warn users about duplicate configuration parameters |
| Date: | 2017-04-07 15:49:12 |
| Message-ID: | CAKFQuwZzgE2BjQ0tqjOCwTpetnJsg_Um2rvCgw813+4FqEK6Cg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Apr 7, 2017 at 8:29 AM, Aleksander Alekseev <
a(dot)alekseev(at)postgrespro(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yorick Peterse | 2017-04-07 15:57:01 | Re: [PATCH] Document the order of changing certain settings when using hot-standby servers |
| Previous Message | Euler Taveira | 2017-04-07 15:48:25 | Re: [PATCH] Warn users about duplicate configuration parameters |