| 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 |
| Subject: | Re: [PATCH] Warn users about duplicate configuration parameters |
| Date: | 2017-04-07 15:17:49 |
| Message-ID: | 20170407151749.3pnrjozc4uprnyi2@alap3.anarazel.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2017-04-07 18:14:27 +0300, Aleksander Alekseev wrote:
> Hi.
>
> Recently I've discovered that if there are multiple values of the same
> parameter in postgresql.conf PostgreSQL will silently use the last one.
> It looks like not the best approach to me. For instance, user can find
> the first value in the config file and expect that it will be used, etc.
>
> I suggest to warn users about duplicated parameters. Here is a
> corresponding patch.
>
> 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.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2017-04-07 15:22:32 | Re: [PATCH] Warn users about duplicate configuration parameters |
| Previous Message | Andres Freund | 2017-04-07 15:15:29 | Re: src/interfaces/libpq shipping nmake-related Makefiles |