Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 6EE04633A7A for ; Tue, 1 Jun 2010 18:50:35 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 27606-02-5 for ; Tue, 1 Jun 2010 21:50:27 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-pw0-f46.google.com (mail-pw0-f46.google.com [209.85.160.46]) by mail.postgresql.org (Postfix) with ESMTP id B328F633854 for ; Tue, 1 Jun 2010 18:50:27 -0300 (ADT) Received: by pwj2 with SMTP id 2so1396610pwj.19 for ; Tue, 01 Jun 2010 14:50:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:cc :subject:references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=t+6xjcq7VXMVXOQUUUP7yA1f6nXr6MpjY9G1wRWHSQ0=; b=Y6sJw+ETF58pYtUIAs/m5OfqrChkxOUxNBNq9qGjhe65yGSSfOivs1EHBI4HK3xMJe lY89mqW3RPheGSHmW7yRjEkM7U7oyt4Ho9B0wUU25xuCZhOte4QDiIiSU1ajdzofAHB/ Z/1l7XCCfdeY7OvNQ4BESt8fCms2fcWumy9JY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:cc:subject:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=Ptei8RyvuCks51qYS/891zIqoDsOgOASVsVIaY7Sv3Ph/ku665Bmb/ttjldpQWssGo cZN1EMiUjOfHbxRhu991iKWM90/0XehTgz2fkkt/oVkXzWTanqq8SQuxlZ9ZRsDS0nHC 4UvLp/jnIGVkZEhIMJ/9X2lKSG4g6pxgEg3ak= Received: by 10.115.37.28 with SMTP id p28mr5688528waj.218.1275429024736; Tue, 01 Jun 2010 14:50:24 -0700 (PDT) Received: from eddie (c-67-182-225-186.hsd1.ut.comcast.net [67.182.225.186]) by mx.google.com with ESMTPS id r20sm62790905wam.17.2010.06.01.14.50.23 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 01 Jun 2010 14:50:23 -0700 (PDT) Message-ID: <4c05809f.1472730a.06d1.600e@mx.google.com> Date: Tue, 1 Jun 2010 15:50:21 -0600 From: Joshua Tolley To: Robert Haas Cc: pgsql-docs@postgresql.org Subject: Re: commit_delay and commit_siblings -- restart or reload? References: <4c052c68.20a5720a.3577.33e6@mx.google.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="YiEDa0DAkWCtVeE4" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-5 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201006/3 X-Sequence-Number: 5571 --YiEDa0DAkWCtVeE4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jun 01, 2010 at 03:33:24PM -0400, Robert Haas wrote: > On Tue, Jun 1, 2010 at 11:51 AM, Joshua Tolley 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 requi= red. >=20 > These parameters are PGC_USERSET - a reload is not the only way to change= them. >=20 > 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 --YiEDa0DAkWCtVeE4 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkwFgJ0ACgkQRiRfCGf1UMN7GgCffnycrj8zAd8y+ylJW2nulBQj 4OMAoJJDiiMaG4FeoV0CxKqj4HNWS0l6 =EdLh -----END PGP SIGNATURE----- --YiEDa0DAkWCtVeE4--