Re: another idea for changing global configuration settings from SQL

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: another idea for changing global configuration settings from SQL
Date: 2012-11-16 17:05:17
Message-ID: CA+TgmoZ66HKgLFBSZ-Dd6s+v0ygDawPP+z7BKU5-WT9VrtA5Tg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Nov 15, 2012 at 5:38 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Another and probably bigger thing is that SIGHUP is used for settings
> that do something useful only in background processes (eg checkpointer).
> Some of those processes are not capable of reading system catalogs at
> all. This is particularly a showstopper for settings affecting the
> postmaster itself, which is most certainly *not* going to grow the
> ability to read catalogs.

This seems like a pretty large strike against this whole idea. In
fact, I think we might want to abandon this whole approach on this
basis.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2012-11-16 17:08:26 Re: Materialized views WIP patch
Previous Message Thom Brown 2012-11-16 17:04:43 Re: Materialized views WIP patch