X-Original-To: pgsql-docs-postgresql.org@localhost.postgresql.org
Received: from localhost (av.hub.org [200.46.204.144])
	by postgresql.org (Postfix) with ESMTP id 5A4449DC9E9
	for <pgsql-docs-postgresql.org@localhost.postgresql.org>;
	Wed,  8 Feb 2006 18:18:06 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 63726-09
	for <pgsql-docs-postgresql.org@localhost.postgresql.org>;
	Wed,  8 Feb 2006 18:18:07 -0400 (AST)
X-Greylist: from auto-whitelisted by SQLgrey-
Received: from smtp.nildram.co.uk (smtp.nildram.co.uk [195.112.4.54])
	by postgresql.org (Postfix) with ESMTP id 9855A9DC89D
	for <pgsql-docs@postgreSQL.org>; Wed,  8 Feb 2006 18:18:03 -0400 (AST)
Received: from [192.168.0.5] (unknown [84.12.26.47])
	by smtp.nildram.co.uk (Postfix) with ESMTP
	id 50ABE257146; Wed,  8 Feb 2006 22:17:49 +0000 (GMT)
Subject: Re: Description of SIGHUP GUC parameters
From: Simon Riggs <simon@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-docs@postgreSQL.org
In-Reply-To: <28949.1137872763@sss.pgh.pa.us>
References: <28949.1137872763@sss.pgh.pa.us>
Content-Type: text/plain
Date: Wed, 08 Feb 2006 22:17:56 +0000
Message-Id: <1139437076.1258.266.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.3 (2.2.3-2.fc4) 
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, score=0.077 required=5 tests=[AWL=0.077]
X-Spam-Score: 0.077
X-Spam-Level: 
X-Archive-Number: 200602/5
X-Sequence-Number: 3445

On Sat, 2006-01-21 at 14:46 -0500, Tom Lane wrote:
> Currently, the standard boilerplate description of a SIGHUP parameter
> is
> 
>         This option can only be set at server start or in the
>         <filename>postgresql.conf</filename> file.
> 
> We've heard from more than one person who found this confusing ---
> frequently it's misread as saying that the parameter cannot be changed
> after postmaster start.  Doubtless this is partly because the
> boilerplate phrase for a POSTMASTER parameter is
> 
>         This option can only be set at server start.
> 
> However, previous discussions have dried up without coming up with a
> better phrase.  It occurred to me today that this might work better:
> 
>         This option can only be set in the <filename>postgresql.conf</>
>         file or on the server command line.
> 
> I think mentioning the config file first is important to focus attention
> on that.  The only other way to set these parameters is via command-line
> switches, so we should just say that rather than emphasizing the "server
> start time" aspect of it, which is exactly what not to emphasize.

Just seen this again today and agree its confusing. 

<wildassertion>I think most people think that all parameters can only be
set at server start, until they have dug deeper. Most other systems
software requires a restart to pick up new parameters</wildassertion>

Why not simply use the technical phrase: "SIGHUP" etc. We can just say
'these terms are shorthand for "......" '

I'm not crazy about the terms but at least it is explicit and accurate.
It would also allow us to have a much longer description of all of the
implications and difficulties of each mode.

Best Regards, Simon Riggs