Re: commit_delay and commit_siblings -- restart or reload? - Mailing list pgsql-docs

From Robert Haas
Subject Re: commit_delay and commit_siblings -- restart or reload?
Date
Msg-id AANLkTimW0kCLOsslenNpOyNN9Gmjf-6zVFVPu9chHdP9@mail.gmail.com
Whole thread Raw
In response to commit_delay and commit_siblings -- restart or reload?  (Joshua Tolley <eggyknap@gmail.com>)
Responses Re: commit_delay and commit_siblings -- restart or reload?  (Joshua Tolley <eggyknap@gmail.com>)
List pgsql-docs
On Tue, Jun 1, 2010 at 11:51 AM, Joshua Tolley <eggyknap@gmail.com> wrote:
> The documentation for commit_delay and commit_siblings doesn't mention whether
> a reload or restart is required to set them. I recommend something like the
> trivial attached docs patch to make it clear(er) that a reload is required.

These parameters are PGC_USERSET - a reload is not the only way to change them.

Of course, changing any parameter in postgresql.conf won't take effect
unless you reload, but the point of that sentence, in the other places
where we use it, is that you can't change those parameters using
things like ALTER DATABASE ... SET, ALTER USER ... SET, just plain
SET, etc.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company

pgsql-docs by date:

Previous
From: Joshua Tolley
Date:
Subject: commit_delay and commit_siblings -- restart or reload?
Next
From: Joshua Tolley
Date:
Subject: Re: commit_delay and commit_siblings -- restart or reload?