| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Josh Kupershmidt <schmiddy(at)gmail(dot)com>, pgsql-docs <pgsql-docs(at)postgresql(dot)org> |
| Subject: | Re: explaining "context" column of pg_settings |
| Date: | 2010-12-18 03:59:40 |
| Message-ID: | 21182.1292644780@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> 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.
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Leslie S Satenstein | 2010-12-20 02:55:29 | Is there a bug list for the version 9.0.2 PDF file |
| Previous Message | Josh Kupershmidt | 2010-12-18 03:46:57 | Re: explaining "context" column of pg_settings |