Re: commit_delay and commit_siblings -- restart or reload?

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Joshua Tolley <eggyknap(at)gmail(dot)com>
Cc: pgsql-docs(at)postgresql(dot)org
Subject: Re: commit_delay and commit_siblings -- restart or reload?
Date: 2010-06-01 19:33:24
Message-ID: AANLkTimW0kCLOsslenNpOyNN9Gmjf-6zVFVPu9chHdP9@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On Tue, Jun 1, 2010 at 11:51 AM, Joshua Tolley <eggyknap(at)gmail(dot)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

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Joshua Tolley 2010-06-01 21:50:21 Re: commit_delay and commit_siblings -- restart or reload?
Previous Message Joshua Tolley 2010-06-01 15:51:02 commit_delay and commit_siblings -- restart or reload?