pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Greg Smith <greg@2ndquadrant.com>
To: Matthew Wakeling <matthew@flymine.org>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Eliot Gable <egable+pgsql-performance@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: B-Heaps
Date: Fri, 18 Jun 2010 13:53:24 -0400
Message-ID: <4C1BB294.8070806@2ndquadrant.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1006181722050.2534@aragorn.flymine.org>
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>

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




view thread (15+ messages)  latest in thread

Message-ID: <4C1BB294.8070806@2ndquadrant.com>
Permalink:  ../4C1BB294.8070806@2ndquadrant.com/
Also on:    postgresql.org/message-id/4C1BB294.8070806@2ndquadrant.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: greg@2ndquadrant.com, matthew@flymine.org, robertmhaas@gmail.com, egable+pgsql-performance@gmail.com
  Subject: Re: B-Heaps
  In-Reply-To: <4C1BB294.8070806@2ndquadrant.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox