| From: | Euler Taveira <euler(at)timbira(dot)com(dot)br> |
|---|---|
| To: | Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Warn users about duplicate configuration parameters |
| Date: | 2017-04-07 15:48:25 |
| Message-ID: | CAHE3wgjt1WjS8gkvBTPX6Kb2PXcBq1q75tvzUfjK6CLe0CcN2w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2017-04-07 12:14 GMT-03:00 Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru>:
> 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.
>
Postgres configuration file concept is based on overriding parameter
values. It would be annoying if we emit warning for this feature. Also, it
is easier to know which file/line the parameter value came from. You can
check for duplicates with a small script.
--
Euler Taveira Timbira - http://www.
timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
<http://www.timbira.com.br>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2017-04-07 15:49:12 | Re: [PATCH] Warn users about duplicate configuration parameters |
| Previous Message | David Steele | 2017-04-07 15:42:45 | Re: [PATCH] Warn users about duplicate configuration parameters |