Thread: SET documentation could mention ALTER USER, etc.

SET documentation could mention ALTER USER, etc.

From
Michael Fuhr
Date:
Suggestion for the SET documentation: mention that settings can be
made permanent by editing postgresql.conf and reloading the postmater,
or by using ALTER USER or ALTER DATABASE.  A place to mention this
might be at the end of the first paragraph under the Description,
after "SET only affects the value used by the current session."

--
Michael Fuhr
http://www.fuhr.org/~mfuhr/

Re: SET documentation could mention ALTER USER, etc.

From
Tom Lane
Date:
Michael Fuhr <mike@fuhr.org> writes:
> Suggestion for the SET documentation: mention that settings can be
> made permanent by editing postgresql.conf and reloading the postmater,
> or by using ALTER USER or ALTER DATABASE.

There's already a link to section 16.4, which explains all that in
detail.

            regards, tom lane

Re: SET documentation could mention ALTER USER, etc.

From
Michael Fuhr
Date:
On Fri, Jan 28, 2005 at 07:20:29PM -0500, Tom Lane wrote:
> Michael Fuhr <mike@fuhr.org> writes:
> > Suggestion for the SET documentation: mention that settings can be
> > made permanent by editing postgresql.conf and reloading the postmater,
> > or by using ALTER USER or ALTER DATABASE.
>
> There's already a link to section 16.4, which explains all that in
> detail.

Sure, but the references say things like "the run-time parameters
listed in Section 16.4" and "Available parameters are documented
in Section 16.4" so somebody might not think to follow the link if
they already know what parameters they're interested in.  It might
be helpful to add another link that says, "And by the way, if you
want to make the changes permanent, see Section 16.4."

--
Michael Fuhr
http://www.fuhr.org/~mfuhr/