Re: [HACKERS] [PATCH] Warn users about duplicate configuration parameters

2017-04-07 Thread David G. Johnston
On Fri, Apr 7, 2017 at 8:29 AM, Aleksander Alekseev < a.aleks...@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 > >

Re: [HACKERS] [PATCH] Warn users about duplicate configuration parameters

2017-04-07 Thread Euler Taveira
2017-04-07 12:14 GMT-03:00 Aleksander Alekseev : > 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 >

Re: [HACKERS] [PATCH] Warn users about duplicate configuration parameters

2017-04-07 Thread David Steele
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

Re: [HACKERS] [PATCH] Warn users about duplicate configuration parameters

2017-04-07 Thread Andres Freund
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

Re: [HACKERS] [PATCH] Warn users about duplicate configuration parameters

2017-04-07 Thread Aleksander Alekseev
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

Re: [HACKERS] [PATCH] Warn users about duplicate configuration parameters

2017-04-07 Thread Tatsuo Ishii
>> 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.

Re: [HACKERS] [PATCH] Warn users about duplicate configuration parameters

2017-04-07 Thread Andres Freund
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

[HACKERS] [PATCH] Warn users about duplicate configuration parameters

2017-04-07 Thread Aleksander Alekseev
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