pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Greg Stark <gsstark@mit.edu>
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: Fri, 27 Aug 2004 00:35:07 -0400 (EDT)
Message-ID: <200408270435.i7R4Z7N25250@candle.pha.pa.us> (raw)
In-Reply-To: <87pt5dnta9.fsf@stark.xeocode.com>


OK, new wording:

        o Automatically maintain clustering on a table

        This might 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.  Another idea would
        be to create a merged heap/index data file so an index lookup would
        automatically access the heap data too.


---------------------------------------------------------------------------

Greg Stark wrote:
> 
> 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
> 

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073



view thread (41+ messages)  latest in thread

Message-ID: <200408270435.i7R4Z7N25250@candle.pha.pa.us>
Permalink:  ../200408270435.i7R4Z7N25250@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200408270435.i7R4Z7N25250@candle.pha.pa.us

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: pgman@candle.pha.pa.us, gsstark@mit.edu, jrogers@neopolitan.com, mha@sollentuna.net, mischa.sandberg@telus.net
  Subject: Re: Equivalent praxis to CLUSTERED INDEX?
  In-Reply-To: <200408270435.i7R4Z7N25250@candle.pha.pa.us>
  References: <87pt5dnta9.fsf@stark.xeocode.com> <200408270435.i7R4Z7N25250@candle.pha.pa.us>

* 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