MIME-Version: 1.0
From: Mahesh Shetty <maheshetty20@gmail.com>
Date: Mon, 4 Aug 2025 10:55:00 +0530
Message-ID: 
 <CAJPiW+hfwGuGQ8fGKSB1-xU6O==eAhVGKrz_FHD3A0KVLv1KRg@mail.gmail.com>
Subject: Indexing Strategy for Partitioned Table in PostgreSQL 15.13
To: pgsql-admin@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000f5d7e7063b835479"
Archived-At: 
 <https://www.postgresql.org/message-id/CAJPiW%2BhfwGuGQ8fGKSB1-xU6O%3D%3DeAhVGKrz_FHD3A0KVLv1KRg%40mail.gmail.com>
Precedence: bulk

--000000000000f5d7e7063b835479
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hello Team,

We=E2=80=99re 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=E2=80=99d appreciate you=
r 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?

Thanks in advance for your guidance.


Regards,

Mahesh

--000000000000f5d7e7063b835479
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><p class=3D"gmail-">Hello Team,</p>
<p class=3D"gmail-">We=E2=80=99re running PostgreSQL version 15.13.</p>
<p class=3D"gmail-">I have a large partitioned table with around 100 partit=
ions, and we&#39;re planning to add an index to it. I&#39;m a bit concerned=
 about the potential impact and duration of the indexing process, and I=E2=
=80=99d appreciate your inputs on the following:</p>
<ol>
<li class=3D"gmail-">
<p class=3D"gmail-">If I run <code>CREATE INDEX CONCURRENTLY</code> on the =
<strong>parent table</strong>, will it automatically create indexes concurr=
ently on all its partitions?</p>
</li>
<li class=3D"gmail-">
<p class=3D"gmail-">Are there any recommended or more efficient approaches =
for indexing a heavily partitioned table that I should consider?</p>
</li>
</ol>
<p class=3D"gmail-">Thanks in advance for your guidance.</p><p class=3D"gma=
il-"><br></p><p class=3D"gmail-">Regards,</p><p class=3D"gmail-">Mahesh</p>=
</div></div>

--000000000000f5d7e7063b835479--