Re: Merging postgresql.conf and postgresql.auto.conf

Поиск
Список
Период
Сортировка
От Amit Kapila
Тема Re: Merging postgresql.conf and postgresql.auto.conf
Дата
Msg-id CAA4eK1J0tNWFQH-_7xGZaGwyUgA-Y40Ay3wjPooyTj7-DjgRDw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Merging postgresql.conf and postgresql.auto.conf  (Sawada Masahiko <sawada.mshk@gmail.com>)
Список pgsql-hackers
On Fri, Jan 16, 2015 at 9:55 PM, Sawada Masahiko <sawada.mshk@gmail.com> wrote:
> On Fri, Jan 16, 2015 at 12:54 PM, Amit Kapila <amit.kapila16@gmail.com> wrote:
> >
> > I don't know how appealing it would be to others, but a new view
> > like pg_file_settings which would display the settings in file could
> > be meaningful for your need.
> >
> > Another way is user can do pg_reload_conf() to see the latest
> > values (excluding values for server startup time parameters).
> >
>
> I prefer the former. Because the latter would not handle all guc
> variables as you said.
> The new view like pg_file_setting has guc variable and config file
> which has corresponding guc variable.
> It would be helpful view for like ALTER SYSTEM ... RESET and that
> command might be beneficial feature for user who want to manage
> configuration file manually, I would like to propose them.
>

Okay, but I think it would be better to start a new thread
as this proposal seems to be different than your original
idea.

With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Lisa Guo
Дата:
Сообщение: Re: n_live_tup smaller than the number of rows in a table
Следующее
От: Amit Kapila
Дата:
Сообщение: Re: Parallel Seq Scan