Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 733061337B2F for ; Fri, 17 Dec 2010 23:59:49 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 03440-09 for ; Sat, 18 Dec 2010 03:59:42 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id 0F62F133798E for ; Fri, 17 Dec 2010 23:59:41 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id oBI3xeSg021183; Fri, 17 Dec 2010 22:59:40 -0500 (EST) To: Robert Haas cc: Josh Kupershmidt , pgsql-docs Subject: Re: explaining "context" column of pg_settings In-reply-to: References: <17754.1292544709@sss.pgh.pa.us> Comments: In-reply-to Robert Haas message dated "Fri, 17 Dec 2010 22:45:32 -0500" Date: Fri, 17 Dec 2010 22:59:40 -0500 Message-ID: <21182.1292644780@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-5 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201012/26 X-Sequence-Number: 6262 Robert Haas writes: > On Fri, Dec 17, 2010 at 10:00 PM, Josh Kupershmidt 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