Message-ID: <4C1BB294.8070806@2ndquadrant.com>
Date: Fri, 18 Jun 2010 13:53:24 -0400
From: Greg Smith <greg@2ndquadrant.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20100317)
MIME-Version: 1.0
To: Matthew Wakeling <matthew@flymine.org>
CC: Robert Haas <robertmhaas@gmail.com>,
	Eliot Gable <egable+pgsql-performance@gmail.com>,
	pgsql-performance@postgresql.org
Subject: Re: B-Heaps
References: <AANLkTinsmWw4w2m2fyjord30seNfn7Ww1arKew5EttQG@mail.gmail.com>
	<alpine.DEB.2.00.1006151313370.4083@aragorn.flymine.org>
	<AANLkTik-81bRcl1tle10YvsdY1F6MwF4SFZErKOZa5LA@mail.gmail.com>
	<alpine.DEB.2.00.1006181722050.2534@aragorn.flymine.org>
In-Reply-To: <alpine.DEB.2.00.1006181722050.2534@aragorn.flymine.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Matthew Wakeling wrote:
> This sort of thing has been fairly well researched at an academic 
> level, but has not been implemented in that many real world 
> situations. I would encourage its use in Postgres.

I guess, but don't forget that work on PostgreSQL is driven by what 
problems people are actually running into.  There's a long list of 
performance improvements sitting in the TODO list waiting for people to 
find time to work on them, ones that we're quite certain are useful.  
That anyone is going to chase after any of these speculative ideas from 
academic research instead of one of those is unlikely.  Your 
characterization of the potential speed up here is "Using a proper tree 
inside the index page would improve the CPU usage of the index lookups", 
which seems quite reasonable.  Regardless, when I consider "is that 
something I have any reason to suspect is a bottleneck on common 
workloads?", I don't think of any, and return to working on one of 
things I already know is instead.

-- 
Greg Smith  2ndQuadrant US  Baltimore, MD
PostgreSQL Training, Services and Support
greg@2ndQuadrant.com   www.2ndQuadrant.us