Re: commit_delay and commit_siblings -- restart or reload?

From: Joshua Tolley <eggyknap(at)gmail(dot)com>
To: Robert Haas <robertmhaas(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 21:50:21
Message-ID: 4c05809f.1472730a.06d1.600e@mx.google.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On Tue, Jun 01, 2010 at 03:33:24PM -0400, Robert Haas wrote:
> 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.

Ah, you're right. My mistake -- thanks.

--
Joshua Tolley / eggyknap
End Point Corporation
http://www.endpoint.com

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message Bruce Momjian 2010-06-03 02:07:02 Re: [PATCH] Explain generate_subscripts() more clearly
Previous Message Robert Haas 2010-06-01 19:33:24 Re: commit_delay and commit_siblings -- restart or reload?