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-01-15T21:58:56Z
Lists: pgsql-hackers
https://commitfest.postgresql.org/patch/6401/

Registered here.

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Revert changes to CONCURRENTLY that "sped up" Xmin advance

  2. VACUUM: ignore indexing operations with CONCURRENTLY