|
1 | 1 | <!-- |
2 | | -$PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.247 2004/03/0916:57:47 neilc Exp $ |
| 2 | +$PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.248 2004/03/0923:15:47 neilc Exp $ |
3 | 3 | --> |
4 | 4 |
|
5 | 5 | <Chapter Id="runtime"> |
@@ -541,11 +541,12 @@ env PGOPTIONS='-c geqo=off' psql |
541 | 541 | SET ENABLE_SEQSCAN TO OFF; |
542 | 542 | </screen> |
543 | 543 | If <command>SET</> is allowed, it overrides all other sources of |
544 | | - values for the parameter. Superusers are allowed to |
545 | | - <command>SET</> more values than ordinary users. Some parameters |
546 | | - cannot be <command>SET</command> even by superusers: for example, |
547 | | - if they control behavior that cannot reasonably be changed without |
548 | | - restarting <productname>PostgreSQL</productname>. |
| 544 | + values for the parameter. Some parameters cannot be changed via |
| 545 | + <command>SET</command>: for example, if they control behavior that |
| 546 | + cannot reasonably be changed without restarting |
| 547 | + <productname>PostgreSQL</productname>. Also, some parameters can |
| 548 | + be modified via <command>SET</command> by superusers, but not by |
| 549 | + ordinary users. |
549 | 550 | </para> |
550 | 551 |
|
551 | 552 | <para> |
|
