From: Greg Stark <gsstark@mit.edu>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: J. Andrew Rogers <jrogers@neopolitan.com>
Cc: Magnus Hagander <mha@sollentuna.net>
Cc: pgsql-performance@postgresql.org
Cc: mischa.sandberg@telus.net
Subject: Re: Equivalent praxis to CLUSTERED INDEX?
Date: 26 Aug 2004 23:39:42 -0400
Message-ID: <87pt5dnta9.fsf@stark.xeocode.com> (raw)
In-Reply-To: <200408270145.i7R1jop04185@candle.pha.pa.us>
References: <200408270145.i7R1jop04185@candle.pha.pa.us>
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> Updated TODO item:
>
> o Automatically maintain clustering on a table
>
> This would require some background daemon to maintain clustering
> during periods of low usage. It might also require tables to be only
> paritally filled for easier reorganization. It also might require
> creating a merged heap/index data file so an index lookup would
> automatically access the heap data too.
Fwiw, I would say the first "would" is also a "might". None of the previous
discussions here presumed a maintenance daemon. The discussions before talked
about a mechanism to try to place new tuples as close as possible to the
proper index position.
I would also suggest making some distinction between a cluster system similar
to what we have now but improved to maintain the clustering continuously, and
an actual index-organized-table where the tuples are actually only stored in a
btree structure.
They're two different approaches to similar problems. But they might both be
useful to have, and have markedly different implementation details.
--
greg
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: gsstark@mit.edu, pgman@candle.pha.pa.us, jrogers@neopolitan.com, mha@sollentuna.net, mischa.sandberg@telus.net
Subject: Re: Equivalent praxis to CLUSTERED INDEX?
In-Reply-To: <87pt5dnta9.fsf@stark.xeocode.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