From: adey <adey11@gmail.com>
To: Chris Hoover <revoohc@gmail.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: best way to choose index to cluster on?
Date: Tue, 26 Sep 2006 10:27:03 +1200
Message-ID: <1c66bda80609251527i4e8bad89jb6c1420cd44a8a33@mail.gmail.com> (raw)
In-Reply-To: <1d219a6f0609251357y33e74c56u4d283af07cd45360@mail.gmail.com>
References: <1d219a6f0609251357y33e74c56u4d283af07cd45360@mail.gmail.com>
A good guide for a clustered index is:-
Will the index be unique, static and narrow.
If not, avoid clustered indexing as they require extra work on disk to
maintain their sequence.
On 9/26/06, Chris Hoover <revoohc@gmail.com> wrote:
>
> I am looking to squeeze a bit more speed out of my database by clustering
> most of my tables. However, on tables with multiple indexes, how is the
> best way to choose the index. I am thinking I want to use the index with
> the largest pg_stat_user_indexes.idx_tup_read. Would this be correct? If
> not, what column(s) and views should I be looking at to find the most
> popular index?
>
> Secondly, I have some partial indexes on a very active table, and it tends
> to have the highest idx_tup_read for that table. Is is possible to cluster
> on a partial index?
>
> Thanks,
>
> Chris
>
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-admin@postgresql.org
Cc: adey11@gmail.com, revoohc@gmail.com
Subject: Re: best way to choose index to cluster on?
In-Reply-To: <1c66bda80609251527i4e8bad89jb6c1420cd44a8a33@mail.gmail.com>
References: <1d219a6f0609251357y33e74c56u4d283af07cd45360@mail.gmail.com> <1c66bda80609251527i4e8bad89jb6c1420cd44a8a33@mail.gmail.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