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
>> t
On Fri, Dec 17, 2010 at 1:08 PM, Euler Taveira de Oliveira
wrote:
> Alvaro Herrera escreveu:
>> Perhaps we can replace the current "this setting requires a restart"
>> boilerplate with "this setting has context foo" in setting descriptions,
>> and have a pointer to wherever the description of each
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 c
On Thu, Dec 16, 2010 at 7:11 PM, Tom Lane wrote:
> Josh Kupershmidt writes:
> I did some work on this patch and attach an updated version.
Thanks for taking a look at this. Your version is much more clear.
> I'm not
> however convinced that it's a good idea to bury this material in
> catalogs.s
Alvaro Herrera escreveu:
> Perhaps we can replace the current "this setting requires a restart"
> boilerplate with "this setting has context foo" in setting descriptions,
> and have a pointer to wherever the description of each context is.
>
.. or even foo_param (integer) (restart)
'restart' is a
Alvaro Herrera writes:
> Excerpts from Tom Lane's message of jue dic 16 21:11:49 -0300 2010:
>> I did some work on this patch and attach an updated version. I'm not
>> however convinced that it's a good idea to bury this material in
>> catalogs.sgml --- I think few people ever read that chapter.
