Re: Indexing Strategy for Partitioned Table in PostgreSQL 15.13 - Mailing list pgsql-admin

From David G. Johnston
Subject Re: Indexing Strategy for Partitioned Table in PostgreSQL 15.13
Date
Msg-id CAKFQuwanhAmgSdh4ou=grR0FiwnM4dEojELmtHTmkyjtJEx5sw@mail.gmail.com
Whole thread Raw
In response to Indexing Strategy for Partitioned Table in PostgreSQL 15.13  (Mahesh Shetty <maheshetty20@gmail.com>)
Responses Re: Indexing Strategy for Partitioned Table in PostgreSQL 15.13
List pgsql-admin
On Sunday, August 3, 2025, Mahesh Shetty <maheshetty20@gmail.com> wrote:

I have a large partitioned table with around 100 partitions, and we're planning to add an index to it. I'm a bit concerned about the potential impact and duration of the indexing process,


It will end very quickly… 

and I’d appreciate your inputs on the following:

  1. If I run CREATE INDEX CONCURRENTLY on the parent table, will it automatically create indexes concurrently on all its partitions?

Sometimes it’s best to just try (I didn’t though)…but the answer is explicitly documented (see create index)

Concurrent builds for indexes on partitioned tables are currently not supported. However, you may concurrently build the index on each partition individually and then finally create the partitioned index non-concurrently in order to reduce the time where writes to the partitioned table will be locked out. In this case, building the partitioned index is a metadata only operation.

David J.

pgsql-admin by date:

Previous
From: Mahesh Shetty
Date:
Subject: Indexing Strategy for Partitioned Table in PostgreSQL 15.13
Next
From: Ron Johnson
Date:
Subject: Re: Vacuuming System DBs like postgres, template1