B-Heaps

From: Eliot Gable <egable+pgsql-performance(at)gmail(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: B-Heaps
Date: 2010-06-15 03:21:30
Message-ID: AANLkTinsmWw4w2m2fyjord30seNfn7Ww1arKew5EttQG@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Just curious if this would apply to PostgreSQL:
http://queue.acm.org/detail.cfm?id=1814327

<http://queue.acm.org/detail.cfm?id=1814327>Now that I've read it, it seems
like a no-brainer. So, how does PostgreSQL deal with the different latencies
involved in accessing data on disk for searches / sorts vs. accessing data
in memory? Is it allocated in a similar way as described in the article such
that disk access is reduced to a minimum?

Responses

  • Re: B-Heaps at 2010-06-15 06:10:10 from Heikki Linnakangas
  • Re: B-Heaps at 2010-06-15 06:40:43 from Greg Smith
  • Re: B-Heaps at 2010-06-15 12:23:43 from Matthew Wakeling

Browse pgsql-performance by date

  From Date Subject
Next Message Scott Carey 2010-06-15 03:27:11 Re: requested shared memory size overflows size_t
Previous Message jgardner@jonathangardner.net 2010-06-15 02:14:46 PostgreSQL as a local in-memory cache