| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | David Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Merging postgresql.conf and postgresql.auto.conf |
| Date: | 2015-01-20 03:41:42 |
| Message-ID: | CAA4eK1JzFM7qt_02RiN=FQPcgLoJWPHu-kF2yBkz8QPgXTJ+zw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jan 20, 2015 at 9:09 AM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
wrote:
>
>
> Right, but we can't completely eliminate such a possibility (as an
> example we have some default settings like max_connections,
> shared_buffers, etc). I agree with you that users should use only
> way
Sorry for incomplete sentence, I mean to say "only one way"
> of changing the settings, however for certain rare cases (default
> settings or some other) we can provide a way for user to know which
> of the settings are duplicate. I think if we can provide such an
> information via some view with ease then it's worth to have it.
>
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2015-01-20 03:47:02 | Re: B-Tree support function number 3 (strxfrm() optimization) |
| Previous Message | Amit Kapila | 2015-01-20 03:39:09 | Re: Merging postgresql.conf and postgresql.auto.conf |