X-Original-To: pgsql-performance@postgresql.org Received: from davinci.ethosmedia.com (unknown [209.10.40.251]) by postgresql.org (Postfix) with ESMTP id 40EBB475CBC for ; Thu, 20 Mar 2003 23:04:09 -0500 (EST) Received: from [63.195.55.98] (HELO spooky) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 2913230; Thu, 20 Mar 2003 20:04:02 -0800 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Organization: Aglio Database Solutions To: "Shridhar Daithankar" , pgsql-performance@postgresql.org Subject: Re: Page Size in Future Releases Date: Thu, 20 Mar 2003 20:03:41 -0800 User-Agent: KMail/1.4.3 References: <200303210909.56451.shridhar_daithankar@persistent.co.in> In-Reply-To: <200303210909.56451.shridhar_daithankar@persistent.co.in> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200303202003.41383.josh@agliodbs.com> X-Archive-Number: 200303/151 X-Sequence-Number: 1449 Shridar, > One reason I know where it would help is getting postgresql to use tons of > shaerd memory. Right now postgresql can not use much beyond 250MB(??) > because number of shared buffer are int or something. So if you know your > reconrds are large, are often manipulated and your OS is not so good at > file caching, then increasing page size might help. Um, two fallacies: 1) You can allocate as much shared buffer ram as you want. The maxium I've tested is 300mb, personally, but I know of no hard limit. 2) However, allocating more shared buffer ram ... in fact anything beyond about 40mb ... has never been shown by anyone on this list to be helpful for any size database, and sometimes the contrary. -- Josh Berkus Aglio Database Solutions San Francisco