Skip site navigation (1) Skip section navigation (2)

pgsql: Remove BufferBlockPointers array in favor of a base + (bufnum) *

From: tgl(at)svr1(dot)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Remove BufferBlockPointers array in favor of a base + (bufnum) *
Date: 2005-08-12 05:05:51
Message-ID: 20050812050551.9BB3D52D8C@svr1.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Log Message:
-----------
Remove BufferBlockPointers array in favor of a base + (bufnum) * BLCKSZ
computation.  On modern machines this is as fast if not faster, and we
don't have to clog the CPU's L2 cache with a tens-of-KB pointer array.
If we ever decide to adopt a more dynamic allocation method for shared
buffers, we'll probably have to revert this patch, but in the meantime
we might as well save a few bytes and nanoseconds.  Per Qingqing Zhou.

Modified Files:
--------------
    pgsql/src/backend/storage/buffer:
        buf_init.c (r1.74 -> r1.75)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/buffer/buf_init.c.diff?r1=1.74&r2=1.75)
        bufmgr.c (r1.192 -> r1.193)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/buffer/bufmgr.c.diff?r1=1.192&r2=1.193)
    pgsql/src/include/storage:
        bufmgr.h (r1.94 -> r1.95)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/storage/bufmgr.h.diff?r1=1.94&r2=1.95)

pgsql-committers by date

Next:From: James William PyeDate: 2005-08-12 05:07:18
Subject: python - be: Move metaend's LargeObject class into prime.py.
Previous:From: James William PyeDate: 2005-08-12 04:26:42
Subject: python - be: Expected is always filled in now, so it cannot be used as

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group