Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 2958B635C2C for ; Tue, 16 Mar 2010 10:52:56 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 15451-05 for ; Tue, 16 Mar 2010 13:52:45 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from 27.mail-out.ovh.net (27.mail-out.ovh.net [91.121.30.210]) by mail.postgresql.org (Postfix) with SMTP id 3E18C6322FB for ; Tue, 16 Mar 2010 10:52:45 -0300 (ADT) Received: (qmail 19838 invoked by uid 503); 16 Mar 2010 13:55:48 -0000 Received: from b9.ovh.net (HELO mail626.ha.ovh.net) (213.186.33.59) by 27.mail-out.ovh.net with SMTP; 16 Mar 2010 13:55:48 -0000 Received: from b0.ovh.net (HELO queueout) (213.186.33.50) by b0.ovh.net with SMTP; 16 Mar 2010 13:53:18 -0000 Received: from par69-8-88-161-102-87.fbx.proxad.net (HELO localhost) (lists%peufeu.com@88.161.102.87) by ns0.ovh.net with SMTP; 16 Mar 2010 13:53:18 -0000 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "Nikolas Everett" Cc: "Greg Smith" , "Dave Crooke" , "Paul McGarry" , pgsql-performance@postgresql.org Subject: Re: shared_buffers advice References: <4B9F3302.4020900@2ndquadrant.com> Date: Tue, 16 Mar 2010 14:48:43 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: "Pierre C" Message-ID: In-Reply-To: User-Agent: Opera Mail/10.10 (Linux) X-Ovh-Tracer-Id: 10181794333656090147 X-Ovh-Remote: 88.161.102.87 (par69-8-88-161-102-87.fbx.proxad.net) X-Ovh-Local: 213.186.33.20 (ns0.ovh.net) X-Spam-Check: DONE|U 0.5/N X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.599 tagged_above=-10 required=5 tests=BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 201003/166 X-Sequence-Number: 37991 > I think the logic you are referring to is the clock sweep buffer > accounting > scheme. That just makes sure that the most popular pages stay in the > buffers. If your entire db fits in the buffer pool then it'll all get in > there real fast. Actually, I meant that in the case of a seq scan, PG will try to use just a few buffers (a ring) in shared_buffers instead of thrashing the whole buffers. But if there was actually a lot of free space in shared_buffers, do the pages stay, or do they not ?