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

Mihail Nikalayeu <mihailnikalayeu@gmail.com>

From: Mihail Nikalayeu <mihailnikalayeu@gmail.com>

To: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Cc: Matthias van de Meent <boekewurm+postgres@gmail.com>, Álvaro Herrera <alvherre@kurilemu.de>, Antonin Houska <ah@cybertec.at>, Sergey Sargsyan <sergey.sargsyan.2001@gmail.com>, Hannu Krosing <hannuk@google.com>

Date: 2026-03-09T00:03:00Z

Lists: pgsql-hackers

Attachments

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

Hello, everyone!

Rebased.

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