public inbox for [email protected]
help / color / mirror / Atom feedFrom: Ron Johnson <[email protected]>
To: pgsql-admin <[email protected]>
Subject: Re: Indexing Strategy for Partitioned Table in PostgreSQL 15.13
Date: Tue, 5 Aug 2025 23:16:39 -0400
Message-ID: <CANzqJaAhS+dKz0yhz0UDSERfBVzbR1A8=oOtprjaQtPe4xB7gw@mail.gmail.com> (raw)
In-Reply-To: <CAJPiW+hfwGuGQ8fGKSB1-xU6O==eAhVGKrz_FHD3A0KVLv1KRg@mail.gmail.com>
References: <CAJPiW+hfwGuGQ8fGKSB1-xU6O==eAhVGKrz_FHD3A0KVLv1KRg@mail.gmail.com>
On Mon, Aug 4, 2025 at 1:25 AM Mahesh Shetty <[email protected]> wrote:
> Hello Team,
>
> We’re running PostgreSQL version 15.13.
>
> 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, 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?
> 2.
>
> Are there any recommended or more efficient approaches for indexing a
> heavily partitioned table that I should consider?
>
> Search for "CREATE INDEX ON ONLY" in
https://www.postgresql.org/docs/15/ddl-partitioning.html
That'll tell you how to build indices in parallel and concurrently.
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
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]
Subject: Re: Indexing Strategy for Partitioned Table in PostgreSQL 15.13
In-Reply-To: <CANzqJaAhS+dKz0yhz0UDSERfBVzbR1A8=oOtprjaQtPe4xB7gw@mail.gmail.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