From: Josh Berkus <josh@agliodbs.com>
To: Bruce Momjian <pgman@candle.pha.pa.us>
To: J. Andrew Rogers <jrogers@neopolitan.com>
Cc: pgsql-performance@postgresql.org
Cc: mischa.sandberg@telus.net
Subject: Re: Equivalent praxis to CLUSTERED INDEX?
Date: Thu, 26 Aug 2004 11:32:30 -0700
Message-ID: <200408261132.30732.josh@agliodbs.com> (raw)
In-Reply-To: <200408261818.i7QIIrr09640@candle.pha.pa.us>
References: <200408261818.i7QIIrr09640@candle.pha.pa.us>
Bruce,
> How do vendors actually implement auto-clustering? I assume they move
> rows around during quiet periods or have lots of empty space in each
> value bucket.
That's how SQL Server does it. In old versions (6.5) you had to manually
send commands to update the cluster, same as PG. Also, when you create a
cluster (or an index or table for that matter) you can manually set an amount
of "space" to be held open on each data page for updates.
Also keep in mind that SQL Server, as a "single-user database" has a much
easier time with this. They don't have to hold several versions of an index
in memory and collapse it into a single version at commit time.
All that being said, we could do a better job of "auto-balancing" clustered
tables. I believe that someone was working on this in Hackers through what
they called "B-Tree Tables". What happened to that?
--
Josh Berkus
Aglio Database Solutions
San Francisco
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: josh@agliodbs.com, pgman@candle.pha.pa.us, jrogers@neopolitan.com, mischa.sandberg@telus.net
Subject: Re: Equivalent praxis to CLUSTERED INDEX?
In-Reply-To: <200408261132.30732.josh@agliodbs.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