| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Neil Conway <neilc(at)samurai(dot)com>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: minor doc work |
| Date: | 2004-03-09 15:35:39 |
| Message-ID: | 200403091635.39185.peter_e@gmx.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Neil Conway wrote:
> 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,
Please don't use marked up command names as verbs. Next week you'll be
<command>UPDATE</command>ing or something. Here, there is no chance for
confusion, so just write "cannot be set" or "cannot be changed with
<command>SET</command>". In fact, the latter is even clearer.
> ! if they control behavior that cannot reasonably be changed without
> ! restarting <productname>PostgreSQL</productname>.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-03-09 15:41:09 | Re: [PATCHES] NO WAIT ... |
| Previous Message | Andrew Dunstan | 2004-03-09 15:02:14 | Re: [PATCHES] log_line_info |