| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru> |
| Cc: | 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:36:21 |
| Message-ID: | 20170407153621.dbvmtisptxzkhb6r@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2017-04-07 18:29:40 +0300, Aleksander Alekseev 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.
More useless warnings make actual warnings less useful.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Steele | 2017-04-07 15:42:45 | Re: [PATCH] Warn users about duplicate configuration parameters |
| Previous Message | Aleksander Alekseev | 2017-04-07 15:29:40 | Re: [PATCH] Warn users about duplicate configuration parameters |