Re: Resetting snapshots during the first phase of [CREATE |RE]INDEX CONCURRENTLY

Mihail Nikalayeu <mihailnikalayeu@gmail.com>

From: Mihail Nikalayeu <mihailnikalayeu@gmail.com>

To: Álvaro Herrera <alvherre@kurilemu.de>

Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Matthias van de Meent <boekewurm+postgres@gmail.com>, Antonin Houska <ah@cybertec.at>, Sergey Sargsyan <sergey.sargsyan.2001@gmail.com>, Hannu Krosing <hannuk@google.com>

Date: 2026-04-06T17:55:00Z

Lists: pgsql-hackers

Attachments

v5-0001-Add-stress-tests-for-concurrent-index-builds.patch (application/octet-stream) patch v5-0001
v5-0004-Support-snapshot-resets-in-concurrent-builds-of-u.patch (application/octet-stream) patch v5-0004
v5-0003-Support-snapshot-resets-in-parallel-concurrent-in.patch (application/octet-stream) patch v5-0003
v5-0002-Reset-snapshots-periodically-in-non-unique-non-pa.patch (application/octet-stream) patch v5-0002

Hello!

0) Rebased
1) Added REPEATABLE READ isolation level
2) Some GUGs for developers
3) Some small refactorings

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