pgsql: Optimize the case where a btree indexscan has current and mark

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Optimize the case where a btree indexscan has current and mark
Date: 2006-08-24 01:18:34
Message-ID: 20060824011834.990639FB1F0@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Optimize the case where a btree indexscan has current and mark positions
on the same index page; we can avoid data copying as well as buffer refcount
manipulations in this common case. Makes for a small but noticeable
improvement in mergejoin speed.

Heikki Linnakangas

Modified Files:
--------------
pgsql/src/backend/access/nbtree:
nbtree.c (r1.149 -> r1.150)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtree.c.diff?r1=1.149&r2=1.150)
nbtsearch.c (r1.105 -> r1.106)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtsearch.c.diff?r1=1.105&r2=1.106)
pgsql/src/include/access:
nbtree.h (r1.103 -> r1.104)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/access/nbtree.h.diff?r1=1.103&r2=1.104)

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2006-08-24 01:41:06 pgsql: Update XML2 documentation for xpath_table().
Previous Message Bruce Momjian 2006-08-23 18:32:02 pgsql: Add "AS" item: < * All backends running as threads in a single