From f28d5614ce48d8812c63cfeb28d0efb9383b3297 Mon Sep 17 00:00:00 2001
From: Neil Conway <neilc@samurai.com>
Date: Tue, 9 Mar 2004 23:15:47 +0000
Subject: [PATCH] Tweak some text to avoid using <command>SET</command> as a
verb, per suggestion from Peter E.
---
doc/src/sgml/runtime.sgml | 13 +++++++------
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index d294c36e29b..310cd96bc39 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.247 2004/03/09 16:57:47 neilc Exp $
+$PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.248 2004/03/09 23:15:47 neilc Exp $
-->
<Chapter Id="runtime">
@@ -541,11 +541,12 @@ 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. 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>.
+ values for the parameter. Some parameters cannot be changed via
+ <command>SET</command>: for example, if they control behavior that
+ cannot reasonably be changed without restarting
+ <productname>PostgreSQL</productname>. Also, some parameters can
+ be modified via <command>SET</command> by superusers, but not by
+ ordinary users.
</para>
<para>
--
GitLab