Re: Free space mapping (was Re: Multi-Versions and Vacuum) - Mailing list pgsql-general

From Tom Lane
Subject Re: Free space mapping (was Re: Multi-Versions and Vacuum)
Date
Msg-id 17393.1030507303@sss.pgh.pa.us
Whole thread Raw
In response to Re: Free space mapping (was Re: Multi-Versions and Vacuum)  (Alvaro Herrera <alvherre@atentus.com>)
List pgsql-general
Alvaro Herrera <alvherre@atentus.com> writes:
> Tom Lane <tgl@sss.pgh.pa.us> escribi�:
>> Eventually we need code to collapse out free space in indexes.

> Maybe when some lower limit is reached in two consecutive pages they
> should be merged?

Yup.  The tricky part is to do this without causing problems for
concurrent readers of the index.

The Lehman-Yao paper that is the basis of our existing code explains how
readers can operate concurrently with splits of index pages.  It doesn't
address doing page merges concurrently with reader scans.  There are
newer papers in the literature that explain how to do that ... but no
one's gotten round to trying to implement it for Postgres.

            regards, tom lane

pgsql-general by date:

Previous
From: Stephan Szabo
Date:
Subject: Re: Screwy behavior with SUM and multiple joins to same
Next
From: Kenneth Been
Date:
Subject: bytea, jdbc, i/o ...