Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1UuRi2-0001dw-Nw for pgsql-docs@arkaria.postgresql.org; Wed, 03 Jul 2013 18:23:18 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1UuRi2-0008Kh-4T for pgsql-docs@arkaria.postgresql.org; Wed, 03 Jul 2013 18:23:18 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1UuRi1-0008Ka-4v for pgsql-docs@postgresql.org; Wed, 03 Jul 2013 18:23:17 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1UuRhw-0008LQ-OR for pgsql-docs@postgresql.org; Wed, 03 Jul 2013 18:23:16 +0000 Received: from bruce by momjian.us with local (Exim 4.72) (envelope-from ) id 1UuRhv-0002or-ML; Wed, 03 Jul 2013 14:23:11 -0400 Date: Wed, 3 Jul 2013 14:23:11 -0400 From: Bruce Momjian To: Satoshi Nagayasu Cc: pgsql-docs@postgresql.org Subject: Re: pg_buffercache description Message-ID: <20130703182311.GC6521@momjian.us> References: <50B037AF.4040900@uptime.jp> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="cNdxnHkX5QqsyA0e" Content-Disposition: inline In-Reply-To: <50B037AF.4040900@uptime.jp> User-Agent: Mutt/1.5.20 (2009-06-14) X-Pg-Spam-Score: -0.0 (/) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org --cNdxnHkX5QqsyA0e Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sat, Nov 24, 2012 at 11:57:51AM +0900, Satoshi Nagayasu wrote: > Hi, > > I found that the manual page for pg_buffercache module explains > "usagecount" as "Page LRU count". > > http://www.postgresql.org/docs/devel/static/pgbuffercache.html > > However, AFAIK, "usagecount" is not a LRU count nowadays, because > LRU is no longer used for the buffer management algorithm. > > I think it should be described as "Clock-sweep count" or something > like that. > > And I'd like to add some additional explanation for the "forknumber" > as below: > > "0 for heap file, 1 for FreeSpaceMap, and 2 for VisibilityMap". > > Any comments? Good suggestion. I ended up referencing the C file that contains the "forknumber" definitions, rather than recreating the list in the docs. I applied the attached patch to head and 9.3. -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. + --cNdxnHkX5QqsyA0e Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="buffer.diff" diff --git a/doc/src/sgml/pgbuffercache.sgml b/doc/src/sgml/pgbuffercache.sgml new file mode 100644 index 1d7d95f..685351f *** a/doc/src/sgml/pgbuffercache.sgml --- b/doc/src/sgml/pgbuffercache.sgml *************** *** 84,90 **** relforknumber smallint ! Fork number within the relation --- 84,91 ---- relforknumber smallint ! Fork number within the relation; see ! include/storage/relfilenode.h *************** *** 98,104 **** usagecount smallint ! Page LRU count --- 99,105 ---- usagecount smallint ! Clock-sweep access count --cNdxnHkX5QqsyA0e Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs --cNdxnHkX5QqsyA0e--