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
> > eve
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
> the first value in the conf
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
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 para
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 pro
>> 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.
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 v
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 sugg
