Rafael Domiciano <rafael.domiciano@xxxxxxxxx> wrote: > this table has about 15 indexes... That would tend to make mass updates like this slow. > How good are to Cluster table? Has any criteria to cluster table? > How can I do it? CLUSTER reads through the table in the sequence of an index, which you specify, and creates a new copy of the table and then replaces the original table with this copy. The table then has no bloat and the data rows will (until you start modifying the table) be in the same sequence as that index. You must have room for a second copy of the table in order for this to succeed. All indexes, permissions, etc. are set to match the original table. The only choice is which index to use -- if there is an index which is often used to select a number of rows, it is a good candidate for use in the CLUSTER, since that will minimize disk access. As has already been pointed out, there are ways to do the same thing with a sequential pass of the data. If there is no index which is often used to select a number of rows, or the CLUSTER is unable to complete in whatever maintenance window you have, the unordered approach might be better than CLUSTER. -Kevin -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
