MIME-Version: 1.0
References: 
 <CADzfLwW9QczZW-E=McxcjUv0e5VMDctQNETbgao0K-SimVhFPA@mail.gmail.com>
 <202505181556.3n6oiowvntyr@alvherre.pgsql>
 <CADzfLwXKtriMnfCNVGNH2ahwXaByjo-QOMWiDTU-9WZqh+zQ5g@mail.gmail.com>
 <CADzfLwW5bDWSxjHK7mqX8Lewki3+5FBydBC+nVcxg4xMGKscyw@mail.gmail.com>
 <CAMAof6-4xaV3QE2ErYJaJhu6qjFn99sWyo_HQeBhHikZM3GexA@mail.gmail.com>
 <CADzfLwXocKhpW3eFP1oScz+m+1XJ3bpi9QmVpoqC9RX9oyX=UA@mail.gmail.com>
 <CAMAof695VA+mbVRhWCTus=E0WnsMAQyqXxfOTohbcb7VUHSP4g@mail.gmail.com>
 <CAMAof69JSL8MYWG2qRScs3RQDpfcyZT_wFwW4SoAvftW+K_p1g@mail.gmail.com>
 <CADzfLwVMtwjHh8KY9kP=_vcYPqHs=JDzuexO4RFQ2fM8VoqovA@mail.gmail.com>
 <CAMAof68L0GO0F0bwuXtLZAjh9k_Hj+o0-8mqfO6iEQyXr4PuVA@mail.gmail.com>
 <CADzfLwUrodAcOggK+3j3LbPLaSXemgHxa-n=LhZTwRAsaakL2g@mail.gmail.com>
 <CAMAof691D4O=3QTuPwJXBYxYpG6s3A=tVhL9vN=T3eeRTMnaig@mail.gmail.com>
 <CADzfLwVT3Y14g6Maz2y92sP2L7rPvpznt+MHM++xiy-U3XMLZQ@mail.gmail.com>
 <CADzfLwXQe9XfQfJs3W-DCPqeqG4rq-6FoYUpGbbpgjcT1Eotpg@mail.gmail.com>
In-Reply-To: 
 <CADzfLwXQe9XfQfJs3W-DCPqeqG4rq-6FoYUpGbbpgjcT1Eotpg@mail.gmail.com>
From: Sergey Sargsyan <sergey.sargsyan.2001@gmail.com>
Date: Mon, 7 Jul 2025 15:00:37 +0300
Message-ID: 
 <CAMAof68kNgwWdkhmZd1ysfyU3PF66Wz+UaUr9g-LJg-_0xBV_Q@mail.gmail.com>
Subject: Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements
To: Mihail Nikalayeu <mihailnikalayeu@gmail.com>
Cc: =?UTF-8?Q?=C3=81lvaro_Herrera?= <alvherre@kurilemu.de>,
	Andres Freund <andres@anarazel.de>, Michael Paquier <michael@paquier.xyz>,
	PostgreSQL Hackers <pgsql-hackers@postgresql.org>,
 Andrey Borodin <amborodin86@gmail.com>,
	Melanie Plageman <melanieplageman@gmail.com>,
	Matthias van de Meent <boekewurm+postgres@gmail.com>
Content-Type: multipart/alternative; boundary="00000000000037e41d063955988d"
Archived-At: 
 <https://www.postgresql.org/message-id/CAMAof68kNgwWdkhmZd1ysfyU3PF66Wz%2BUaUr9g-LJg-_0xBV_Q%40mail.gmail.com>
Precedence: bulk

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

I=E2=80=99ve tested the patch across several thousand test cases, and no fa=
ults of
any kind have been observed.
Additionally, I independently built a closed banking transaction system to
verify consistency during REINDEX CONCURRENTLY while multiple backends were
writing simultaneously. The results showed no missing transactions, and the
validation logic worked exactly as expected. On large tables, I observed a
significant speedup=E2=80=94often several times faster.

I believe this patch is highly valuable, as REINDEX CONCURRENTLY is a
common maintenance operation. I also noticed that there is a separate
thread working on adding support for concurrent reindexing of partitioned
indexes. Without this patch, that feature would likely suffer from serious
performance issues due to the need to reindex many indexes in one go=E2=80=
=94making
the process both time-consuming and lock-intensive.

Best regards,
S

On Thu, Jul 3, 2025, 3:24=E2=80=AFAM Mihail Nikalayeu <mihailnikalayeu@gmai=
l.com>
wrote:

> Hello!
>
> Rebased again, patch structure and comments available here [0]. Quick
> introduction poster - here [1].
>
> Best regards,
> Mikhail.
>
> [0]:
> https://www.postgresql.org/message-id/flat/CADzfLwVOcZ9mg8gOG%2BKXWurt%3D=
MHRcqNv3XSECYoXyM3ENrxyfQ%40mail.gmail.com#52c97e004b8f628473124c05e3bf2da1
> [1]:
> https://www.postgresql.org/message-id/attachment/176651/STIR-poster.pdf
>

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

<div dir=3D"auto">I=E2=80=99ve tested the patch across several thousand tes=
t cases, and no faults of any kind have been observed.<div dir=3D"auto"></d=
iv><div dir=3D"auto">Additionally, I independently built a closed banking t=
ransaction system to verify consistency during REINDEX CONCURRENTLY while m=
ultiple backends were writing simultaneously. The results showed no missing=
 transactions, and the validation logic worked exactly as expected. On larg=
e tables, I observed a significant speedup=E2=80=94often several times fast=
er.</div><div dir=3D"auto"><br></div><div dir=3D"auto">I believe this patch=
 is highly valuable, as REINDEX CONCURRENTLY is a common maintenance operat=
ion. I also noticed that there is a separate thread working on adding suppo=
rt for concurrent reindexing of partitioned indexes. Without this patch, th=
at feature would likely suffer from serious performance issues due to the n=
eed to reindex many indexes in one go=E2=80=94making the process both time-=
consuming and lock-intensive.</div><div dir=3D"auto"><br></div><div dir=3D"=
auto">Best regards,=C2=A0</div><div dir=3D"auto">S</div></div><br><div clas=
s=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" class=3D"gmail_att=
r">On Thu, Jul 3, 2025, 3:24=E2=80=AFAM Mihail Nikalayeu &lt;<a href=3D"mai=
lto:mihailnikalayeu@gmail.com">mihailnikalayeu@gmail.com</a>&gt; wrote:<br>=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex">Hello!<br>
<br>
Rebased again, patch structure and comments available here [0]. Quick<br>
introduction poster - here [1].<br>
<br>
Best regards,<br>
Mikhail.<br>
<br>
[0]: <a href=3D"https://www.postgresql.org/message-id/flat/CADzfLwVOcZ9mg8g=
OG%2BKXWurt%3DMHRcqNv3XSECYoXyM3ENrxyfQ%40mail.gmail.com#52c97e004b8f628473=
124c05e3bf2da1" rel=3D"noreferrer noreferrer" target=3D"_blank">https://www=
.postgresql.org/message-id/flat/CADzfLwVOcZ9mg8gOG%2BKXWurt%3DMHRcqNv3XSECY=
oXyM3ENrxyfQ%40mail.gmail.com#52c97e004b8f628473124c05e3bf2da1</a><br>
[1]: <a href=3D"https://www.postgresql.org/message-id/attachment/176651/STI=
R-poster.pdf" rel=3D"noreferrer noreferrer" target=3D"_blank">https://www.p=
ostgresql.org/message-id/attachment/176651/STIR-poster.pdf</a><br>
</blockquote></div>

--00000000000037e41d063955988d--