pgsql: A couple of tiny performance hacks in _bt_step(). - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: A couple of tiny performance hacks in _bt_step().
Date
Msg-id 20051207180348.DB1E39DCABF@postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
A couple of tiny performance hacks in _bt_step().  Remove PageIsEmpty
checks, which were once needed because PageGetMaxOffsetNumber would
fail on empty pages, but are now just redundant.  Also, don't set up
local variables that aren't needed in the fast path --- most of the
time, we only need to advance offnum and not step across a page boundary.
Motivated by noticing _bt_step at the top of OProfile profile for a
pgbench run.

Modified Files:
--------------
    pgsql/src/backend/access/nbtree:
        nbtsearch.c (r1.97 -> r1.98)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtsearch.c.diff?r1=1.97&r2=1.98)

pgsql-committers by date:

Previous
From: momjian@postgresql.org (Bruce Momjian)
Date:
Subject: pgsql: Update: < at initdb time or optionally later.
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Push the responsibility for handling ignore_killed_tuples down