Hi All,

I have an app that updates a PostgreSQL db in a batch fashion.  After
each batch (or several batches), it issues VACUUM and ANALYZE calls on
the updated tables.  Now I want to cluster some tables for better
performance.  I understand that doing a VACUUM and a CLUSTER on a table
is wasteful as the CLUSTER makes the VACUUM superfluous.  The app does
not have a built-in list of the tables and whether each is clustered or
not.  It looks to me as if the only way to determine whether to issue a
VACUUM (on a non-clustered table) or a CLUSTER (on a clustered table) is
to query the table "pg_index", much like view "pg_indexes" does, for the
column "indisclustered".  Is this right?

Also, how expensive is CLUSTER compared to VACUUM?  Does CLUSTER read in
the whole table, sort it, and write it back out?  Or write out a
completely new file?  Is the time for a CLUSTER the same whether one row
is out of place or the table is completely disordered?

Thanks,
Ken



---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
      subscribe-nomail command to [EMAIL PROTECTED] so that your
      message can get through to the mailing list cleanly

Reply via email to