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

From: Mihail Nikalayeu <mihailnikalayeu(at)gmail(dot)com>
To: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Antonin Houska <ah(at)cybertec(dot)at>, Sergey Sargsyan <sergey(dot)sargsyan(dot)2001(at)gmail(dot)com>, Hannu Krosing <hannuk(at)google(dot)com>
Subject: Re: Resetting snapshots during the first phase of [CREATE |RE]INDEX CONCURRENTLY
Date: 2026-04-11 17:48:00
Message-ID: CADzfLwXbXodvQFp1XYBt_vjf0em0cFpWOnLFqFGop9uWavYzBA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Rebased +

1) extract duplicate key error reporting into _bt_report_duplicate()
2) limit heap fetches in the tuplesort fail-fast duplicate check to a
configurable percentage

Best regards,
Mikhail.

Attachment Content-Type Size
v5-0001-Add-stress-tests-for-concurrent-index-builds.patch application/octet-stream 12.6 KB
v5-0003-Support-snapshot-resets-in-parallel-concurrent-in.patch application/octet-stream 38.9 KB
v5-0002-Reset-snapshots-periodically-in-non-unique-non-pa.patch application/octet-stream 52.5 KB
v5-0004-Support-snapshot-resets-in-concurrent-builds-of-u.patch application/octet-stream 41.9 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Shlok Kyal 2026-04-11 19:02:40 Re: Support EXCEPT for ALL SEQUENCES publications
Previous Message Mihail Nikalayeu 2026-04-11 16:56:00 Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements