From: Stephan Szabo <sszabo@megazone23.bigpanda.com>
To: Jean-Luc Lachance <jllachan@nsd.ca>
Cc: pgsql-general@postgresql.org
Cc: pgsql-performance@postgresql.org
Subject: Re: CLUSTER command
Date: Thu, 12 Dec 2002 14:03:56 -0800 (PST)
Message-ID: <20021212135913.Q11714-100000@megazone23.bigpanda.com> (raw)
In-Reply-To: <3DF90042.E5290B7F@nsd.ca>
On Thu, 12 Dec 2002, Jean-Luc Lachance wrote:
> Hi all,
>
> I just read about the cluster command and was a little (very)
> disapointed.
> Clustered tables do not remain clustered after inserts.
> Clustered tables are usefull when the table is very large and there are
> few different keys.
>
>
> Because the table file is already extended (2G limit) using different
> files extension (.N)
> how complicated (modifying the code) would it be to have the table files
> split according to the cluster key?
I'd vote against changing the existing CLUSTER since the existing CLUSTER
while not great does handle many different key values fairly well as well
and this solution wouldn't. Many different key values are still
useful to cluster if you're doing searches over ranges since it lowers the
number of heap file reads necessary. If done this should probably be
separate from the existing cluster or at least both versions should be
possible.
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-interfaces@postgresql.org
Cc: sszabo@megazone23.bigpanda.com, jllachan@nsd.ca, pgsql-general@postgresql.org, pgsql-performance@postgresql.org
Subject: Re: CLUSTER command
In-Reply-To: <20021212135913.Q11714-100000@megazone23.bigpanda.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