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

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, 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-22 17:27:22
Message-ID: CA+TgmoYvnCV6z33zmF85MVZTg+MPkz6_9n0WohD-zrtZT_Obxw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jan 21, 2015 at 11:13 AM, Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com> wrote:
> I think this new view is updated only when postmaster received SIGHUP
> or is started.
> And we can have new function like pg_update_file_setting() which
> updates this view.

I really don't think the postmaster should be in the business of
trying to publish views of the data. Let the individual backend
reveal its own view, and keep the postmaster out of it.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2015-01-22 17:46:01 Re: TODO : Allow parallel cores to be used by vacuumdb [ WIP ]
Previous Message Robert Haas 2015-01-22 17:26:12 Re: Merging postgresql.conf and postgresql.auto.conf