From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Josh Kupershmidt <schmiddy@gmail.com>
Cc: pgsql-docs <pgsql-docs@postgresql.org>
Subject: Re: explaining "context" column of pg_settings
Date: Fri, 17 Dec 2010 22:59:40 -0500
Message-ID: <21182.1292644780@sss.pgh.pa.us> (raw)
In-Reply-To: <AANLkTi=p73tGObduA7CYy3pLj5tYw+VU_R8EM49fVThx@mail.gmail.com>
References: <AANLkTi=rY=Ffo3JkU1eKROG0cDnr0PKaejrEbTSjffnu@mail.gmail.com>
<17754.1292544709@sss.pgh.pa.us>
<AANLkTim-L4kff5vovmdx5RS21fPYdzYNw6g4iay6ahXh@mail.gmail.com>
<AANLkTi=p73tGObduA7CYy3pLj5tYw+VU_R8EM49fVThx@mail.gmail.com>
Robert Haas <robertmhaas@gmail.com> writes:
> On Fri, Dec 17, 2010 at 10:00 PM, Josh Kupershmidt <schmiddy@gmail.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.
Yeah. It is documented somewhere in the SGML docs, IIRC, but I'm not
sure we want it up on the marquee.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: tgl@sss.pgh.pa.us, robertmhaas@gmail.com, schmiddy@gmail.com
Subject: Re: explaining "context" column of pg_settings
In-Reply-To: <21182.1292644780@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox