X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 610D2D1B8A5 for ; Thu, 4 Sep 2003 00:05:38 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 63078-05 for ; Wed, 3 Sep 2003 21:05:09 -0300 (ADT) Received: from ganymede.hub.org (u173n10.eastlink.ca [24.224.173.10]) by svr1.postgresql.org (Postfix) with ESMTP id 7773DD1B91B for ; Wed, 3 Sep 2003 21:05:06 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id A08E03405A; Wed, 3 Sep 2003 21:04:58 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 900F033C8A; Wed, 3 Sep 2003 21:04:58 -0300 (ADT) Date: Wed, 3 Sep 2003 21:04:58 -0300 (ADT) From: "Marc G. Fournier" To: Bruce Momjian Cc: Vivek Khera , pgsql-performance@postgresql.org Subject: Re: FreeBSD page size In-Reply-To: <200309032329.h83NTOm14572@candle.pha.pa.us> Message-ID: <20030903210400.U803@ganymede.hub.org> References: <200309032329.h83NTOm14572@candle.pha.pa.us> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/34 X-Sequence-Number: 3400 On Wed, 3 Sep 2003, Bruce Momjian wrote: > Vivek Khera wrote: > > the restore complained often about checkpoints occurring every few > > seconds: > > > > Sep 2 11:57:14 d02 postgres[49721]: [5-1] LOG: checkpoints are occurring too frequently (15 seconds apart) > > Sep 2 11:57:14 d02 postgres[49721]: [5-2] HINT: Consider increasing CHECKPOINT_SEGMENTS. > > > > The HINT threw me off since I had to set checkpoint_segments in > > postgresql.conf, where as CHECKPOINT_SEGMENTS implied to me a > > compile-time constant. > > Woo hoo, my warning worked. Great. > > I uppercased it because config parameters are uppercased in the > documentation. Do we mention config parameters in any other error > messages? Should it be lowercased? k, to me upper case denotes a compiler #define, so I would have been confused ... I'd go with lower case and single quotes around it to denote its a variable to be changed ...