Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements

Mihail Nikalayeu <mihailnikalayeu@gmail.com>

From: Mihail Nikalayeu <mihailnikalayeu@gmail.com>

To: Matthias van de Meent <boekewurm+postgres@gmail.com>

Cc: Antonin Houska <ah@cybertec.at>, Hannu Krosing <hannuk@google.com>, Sergey Sargsyan <sergey.sargsyan.2001@gmail.com>, Álvaro 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>

Date: 2026-01-15T22:04:19Z

Lists: pgsql-hackers

Hello!

Matthias van de Meent <boekewurm+postgres@gmail.com>:

> > Also, I think I'll extract reset-snapshot for CIC in a separate CF
> > entry, since it still may be used with or without either STIR or LR.
>
> Thanks!
>

Registered here: https://commitfest.postgresql.org/patch/6401/

Mikhail.

>

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Revert changes to CONCURRENTLY that "sped up" Xmin advance
- e28bb8851969 15.0 cited
VACUUM: ignore indexing operations with CONCURRENTLY
- d9d076222f5b 14.0 cited
Avoid spurious waits in concurrent indexing
- c98763bf51bf 14.0 cited