From cb659ecb409ae94941568e8216ab81a7331c5443 Mon Sep 17 00:00:00 2001
From: Neil Conway <neilc@samurai.com>
Date: Sun, 7 Mar 2004 01:02:55 +0000
Subject: [PATCH] Explicitely mention that some GUC variables cannot be changed
 at runtime.

---
 doc/src/sgml/runtime.sgml | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index f64719bd78..5c67f70863 100644
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.244 2004/03/05 23:16:17 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.245 2004/03/07 01:02:55 neilc Exp $
 -->
 
 <Chapter Id="runtime">
@@ -541,8 +541,11 @@ env PGOPTIONS='-c geqo=off' psql
 SET ENABLE_SEQSCAN TO OFF;
 </screen>
     If <command>SET</> is allowed, it overrides all other sources of
-    values for the parameter.  Superusers are allowed to <command>SET</>
-    more values than ordinary users.
+    values for the parameter.  Superusers are allowed to
+    <command>SET</> more values than ordinary users.  Some parameters
+    cannot be <command>SET</command> even by superusers: for example,
+    if they control behavior that cannot reasonably be changed without
+    restarting <productname>PostgreSQL</productname>.
    </para>
 
    <para>