Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id DDFD865010B for ; Thu, 30 Oct 2008 14:00:34 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 56579-10 for ; Thu, 30 Oct 2008 14:00:31 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by postgresql.org (Postfix) with ESMTP id 53AA964FDF3 for ; Thu, 30 Oct 2008 14:00:31 -0300 (ADT) Received: from perhan.alvh.no-ip.org (200-126-101-5.bk7-dsl.surnet.cl [200.126.101.5]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id m9UH4eHE007379 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 30 Oct 2008 10:04:42 -0700 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id AC46F47CBC; Thu, 30 Oct 2008 14:00:23 -0300 (CLST) Date: Thu, 30 Oct 2008 14:00:23 -0300 From: Alvaro Herrera To: "Joshua D. Drake" Cc: Scott Carey , Christiaan Willemsen , pgsql-performance@postgresql.org Subject: Re: Configuring for maximum memory usage Message-ID: <20081030170023.GH3857@alvh.no-ip.org> References: <4909CF9C.80701@technocon.com> <4909D688.1090806@commandprompt.com> <4909D989.5020905@technocon.com> <1225382752.32621.4.camel@jd-laptop.pragmaticzealot.org> <1225385730.32621.21.camel@jd-laptop.pragmaticzealot.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1225385730.32621.21.camel@jd-laptop.pragmaticzealot.org> User-Agent: Mutt/1.5.18 (2008-05-17) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Thu, 30 Oct 2008 10:04:43 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200810/127 X-Sequence-Number: 31708 Joshua D. Drake wrote: > However that isn't the exact same thing as a "cache" at least as I was > trying to describe it. shared buffers are used to keep track of pages > (as well as some other stuff) and their current status. That is not the > same as caching a relation. Um, having a page in shared buffers means exactly that the page is cached (a.k.a. it won't have to be read from the lower level next time). -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.