Question: How do you cluster a table in PostgreSQL to optimize query performance?


In PostgreSQL, "clustering" refers to the operation of reordering the physical order of rows in a table to match the index. This can significantly enhance performance for certain queries, especially range queries that fetch large sets of contiguous rows.

Why Cluster Tables?

Clustering can be beneficial when you have a table where:

  • You frequently run queries that retrieve large blocks of data sequentially.
  • The table has a well-defined ordering that benefits these queries, typically through an index.

Clustering is particularly effective for tables that are read-heavy and do not undergo frequent updates, as updates can disrupt the physical order enforced by clustering.

How to Cluster Tables

To cluster a table in PostgreSQL, you follow these steps:

  1. Create an Index: First, create an index on the column(s) that you often use for filtering your queries.

    CREATE INDEX idx_employee_on_join_date ON employee(join_date);
  2. Cluster the Table: After creating the index, you can cluster the table using that index.

    CLUSTER employee USING idx_employee_on_join_date;

    This command will reorder the employee table physically on disk to match the order of the idx_employee_on_join_date index.

  3. Maintaining Clusters: Since PostgreSQL does not automatically maintain the clustered order after further DML (Data Manipulation Language) operations like INSERTs, UPDATEs, or DELETEs, you will need to periodically re-cluster the table. This can be done by reissuing the CLUSTER command.

    CLUSTER employee USING idx_employee_on_join_date;

Alternatively, if you wish to enforce a re-clustering without specifying the index again, you can use:

CLUSTER employee;

This assumes the table was previously clustered with an index, and PostgreSQL remembers this.


  • Locking: The CLUSTER command locks the table, so it cannot be accessed for writing during the process. Ensure minimal disruption by scheduling clustering during low-usage periods.
  • Disk Space: Clustering requires additional disk space, approximately equal to the size of the table, because it essentially creates a new copy of the table sorted and then drops the old one.
  • Usage Frequency: Due to its need for re-running and the resource-intensive nature, clustering might not be suitable for all environments. Analyze the performance gains versus the operational overhead before deciding to implement clustering.

By carefully selecting which tables and indexes to cluster and maintaining them appropriately, you can leverage clustering to enhance the performance of your database for specific workload patterns.

Was this content helpful?

White Paper

Free System Design on AWS E-Book

Download this early release of O'Reilly's latest cloud infrastructure e-book: System Design on AWS.

Free System Design on AWS E-Book
Start building today

Dragonfly is fully compatible with the Redis ecosystem and requires no code changes to implement.