Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id D6135632BCE for ; Fri, 3 Apr 2009 15:17:45 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 69840-05 for ; Fri, 3 Apr 2009 15:17:44 -0300 (ADT) Received: from cvs.postgresql.org (cvs.postgresql.org [217.196.146.206]) by mail.postgresql.org (Postfix) with ESMTP id 74B5C632B96 for ; Fri, 3 Apr 2009 15:17:44 -0300 (ADT) Received: by cvs.postgresql.org (Postfix, from userid 1007) id 63F0A754ADE; Fri, 3 Apr 2009 18:17:43 +0000 (UTC) MIME-Version: 1.0 To: pgsql-committers@postgresql.org Subject: pgsql: Add a comment documenting the question of whether PrefetchBuffer X-Mailer: activitymail 1.24, http://search.cpan.org/dist/activitymail/ Content-Type: text/plain Message-Id: <20090403181743.63F0A754ADE@cvs.postgresql.org> Date: Fri, 3 Apr 2009 18:17:43 +0000 (UTC) From: tgl@postgresql.org (Tom Lane) 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: 200904/39 X-Sequence-Number: 36533 Log Message: ----------- Add a comment documenting the question of whether PrefetchBuffer should try to protect an already-existing buffer from being evicted. This was left as an open issue when the posix_fadvise patch was committed. I'm not sure there's any evidence to justify more work in this area, but we should have some record about it in the source code. Modified Files: -------------- pgsql/src/backend/storage/buffer: bufmgr.c (r1.250 -> r1.251) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/buffer/bufmgr.c?r1=1.250&r2=1.251)