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

pgsql: Make heap_fetch API more consistent by having the buffer remain

From: tgl(at)svr1(dot)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Make heap_fetch API more consistent by having the buffer remain
Date: 2004-10-26 16:05:03
Message-ID: 20041026160503.9B6E03A4450@svr1.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Log Message:
-----------
Make heap_fetch API more consistent by having the buffer remain pinned
in all cases when keep_buf = true.  This allows ANALYZE's inner loop to
use heap_release_fetch, which saves multiple buffer lookups for the same
page and avoids overestimation of cost by the vacuum cost mechanism.

Modified Files:
--------------
    pgsql/src/backend/access/heap:
        heapam.c (r1.179 -> r1.180)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/heap/heapam.c.diff?r1=1.179&r2=1.180)
    pgsql/src/backend/access/nbtree:
        nbtinsert.c (r1.117 -> r1.118)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtinsert.c.diff?r1=1.117&r2=1.118)
    pgsql/src/backend/commands:
        analyze.c (r1.77 -> r1.78)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/analyze.c.diff?r1=1.77&r2=1.78)

pgsql-committers by date

Next:From: Bruce MomjianDate: 2004-10-26 17:28:28
Subject: pgsql: Update Russian FAQ.
Previous:From: Tom LaneDate: 2004-10-25 15:42:02
Subject: pgsql: In the new dispensation where REINDEX doesn't take exclusive lock

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