public inbox for [email protected]
help / color / mirror / Atom feedFrom: DINESH NAIR <[email protected]>
To: David G. Johnston <[email protected]>
To: Mahesh Shetty <[email protected]>
Cc: Pgsql-admin <[email protected]>
Subject: Re: Indexing Strategy for Partitioned Table in PostgreSQL 15.13
Date: Wed, 6 Aug 2025 02:40:33 +0000
Message-ID: <PN4P287MB4381D8F12608B6572F14A5C89C22A@PN4P287MB4381.INDP287.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CAKFQuwanhAmgSdh4ou=grR0FiwnM4dEojELmtHTmkyjtJEx5sw@mail.gmail.com>
References: <CAJPiW+hfwGuGQ8fGKSB1-xU6O==eAhVGKrz_FHD3A0KVLv1KRg@mail.gmail.com>
<CAKFQuwanhAmgSdh4ou=grR0FiwnM4dEojELmtHTmkyjtJEx5sw@mail.gmail.com>
Hi,
For partition tables concurrent indexes are not supported(checked in postgres 17.5 version )
Work around will be to create normal indexes on the main table.
Thanks
Dinesh Nair
________________________________
From: David G. Johnston <[email protected]>
Sent: Monday, August 4, 2025 11:05 AM
To: Mahesh Shetty <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: Indexing Strategy for Partitioned Table in PostgreSQL 15.13
Caution: This email was sent from an external source. Please verify the sender’s identity before clicking links or opening attachments.
On Sunday, August 3, 2025, Mahesh Shetty <[email protected]<mailto:[email protected]>> 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.
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: Indexing Strategy for Partitioned Table in PostgreSQL 15.13
In-Reply-To: <PN4P287MB4381D8F12608B6572F14A5C89C22A@PN4P287MB4381.INDP287.PROD.OUTLOOK.COM>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox