Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 1167B1337B3E for ; Wed, 3 Nov 2010 13:52:28 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 56124-02 for ; Wed, 3 Nov 2010 16:52:21 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mh3.mail.rice.edu (mh3.mail.rice.edu [128.42.199.10]) by mail.postgresql.org (Postfix) with ESMTP id 990841335B36 for ; Wed, 3 Nov 2010 13:52:20 -0300 (ADT) Received: from mh3.mail.rice.edu (localhost.localdomain [127.0.0.1]) by mh3.mail.rice.edu (Postfix) with ESMTP id EAB7128F701; Wed, 3 Nov 2010 11:52:19 -0500 (CDT) X-Virus-Scanned: by amavis-2.6.4 at mh3.mail.rice.edu, auth channel Received: from mh3.mail.rice.edu ([127.0.0.1]) by mh3.mail.rice.edu (mh3.mail.rice.edu [127.0.0.1]) (amavis, port 10026) with ESMTP id 4SGldUiK3OKf; Wed, 3 Nov 2010 11:52:17 -0500 (CDT) X-SMTP-Auth: no X-SMTP-Auth: no Received: from aart.is.rice.edu (aart.is.rice.edu [168.7.56.48]) by mh3.mail.rice.edu (Postfix) with ESMTP id 8326B28F6FE; Wed, 3 Nov 2010 11:52:17 -0500 (CDT) Received: by aart.is.rice.edu (Postfix, from userid 18612) id D04712D5A6; Wed, 3 Nov 2010 11:52:16 -0500 (CDT) Date: Wed, 3 Nov 2010 11:52:16 -0500 From: Kenneth Marshall To: Mladen Gogala Cc: "pgsql-performance@postgresql.org" Subject: Re: Bufer cache replacement LRU algorithm? Message-ID: <20101103165216.GC27429@aart.is.rice.edu> References: <4CD18F55.6070100@vmsinfo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4CD18F55.6070100@vmsinfo.com> User-Agent: Mutt/1.5.16 (2007-06-09) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-4.21 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201011/27 X-Sequence-Number: 41051 Mladen, You would need to check the mailing lists. The release notes have it as being a clock sweep algorithm starting in version 8. Then additional changes were added to eliminate the cache blowout caused by a sequential scan and by vacuum/autovacuum. I do not believe that there are any parameters available other than total size of the pool and whether sequential scans are synchronized. Regards, Ken On Wed, Nov 03, 2010 at 12:35:33PM -0400, Mladen Gogala wrote: > Where can I find the documentation describing the buffer replacement > policy? Are there any parameters governing the page replacement policy? > > -- > Mladen Gogala Sr. Oracle DBA > 1500 Broadway > New York, NY 10036 > (212) 329-5251 > http://www.vmsinfo.com The Leader in Integrated Media Intelligence > Solutions > > > > > -- > Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-performance >