From: | David Steele <david(at)pgmasters(dot)net> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCH] Warn users about duplicate configuration parameters |
Date: | 2017-04-07 15:42:45 |
Message-ID: | ebe3c2bd-1cb1-89c5-7c60-87a0f8fcdabe@pgmasters.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 4/7/17 11:22 AM, Tatsuo Ishii wrote:
>>> 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.
>
> -1 from me too by the same reason Andres said.
-1 from me for the same reason.
--
-David
david(at)pgmasters(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Euler Taveira | 2017-04-07 15:48:25 | Re: [PATCH] Warn users about duplicate configuration parameters |
Previous Message | Andres Freund | 2017-04-07 15:36:21 | Re: [PATCH] Warn users about duplicate configuration parameters |