Re: Indexing Strategy for Partitioned Table in PostgreSQL 15.13
| От | David G. Johnston |
|---|---|
| Тема | Re: Indexing Strategy for Partitioned Table in PostgreSQL 15.13 |
| Дата | |
| Msg-id | CAKFQuwanhAmgSdh4ou=grR0FiwnM4dEojELmtHTmkyjtJEx5sw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Indexing Strategy for Partitioned Table in PostgreSQL 15.13 (Mahesh Shetty <maheshetty20@gmail.com>) |
| Ответы |
Re: Indexing Strategy for Partitioned Table in PostgreSQL 15.13
|
| Список | 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:
If I run
CREATE INDEX CONCURRENTLYon 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 по дате отправления: