Skip site navigation (1) Skip section navigation (2)

Re: explaining "context" column of pg_settings

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Josh Kupershmidt <schmiddy(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-docs <pgsql-docs(at)postgresql(dot)org>
Subject: Re: explaining "context" column of pg_settings
Date: 2010-12-18 03:45:32
Message-ID: AANLkTi=p73tGObduA7CYy3pLj5tYw+VU_R8EM49fVThx@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-docs
On Fri, Dec 17, 2010 at 10:00 PM, Josh Kupershmidt <schmiddy(at)gmail(dot)com> wrote:
> I was rather surprised when I learned this from the description in
> guc.h of SIGHUP options. I tested by altering "full_page_writes" in
> postgresql.conf and sending a SIGHUP to one backend, and sure enough
> that backend picked up the change but new backends didn't. Unless this
> feature is documented somewhere else, I think it would be helpful to
> keep a snippet like this.

I'm not sure we want people to rely on that behavior.  Had we a way of
being sure that all backends would see an updated value at the same
time, we might be able to make some things that are PGC_POSTMASTER to
be PGC_SIGHUP instead.

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

In response to

Responses

pgsql-docs by date

Next:From: Josh KupershmidtDate: 2010-12-18 03:46:57
Subject: Re: explaining "context" column of pg_settings
Previous:From: Josh KupershmidtDate: 2010-12-18 03:00:41
Subject: Re: explaining "context" column of pg_settings

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group