Re: Adding REPACK [concurrently]

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Antonin Houska <ah(at)cybertec(dot)at>
Cc: Srinath Reddy Sadipiralla <srinath2133(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Mihail Nikalayeu <mihailnikalayeu(at)gmail(dot)com>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Robert Treat <rob(at)xzilla(dot)net>
Subject: Re: Adding REPACK [concurrently]
Date: 2026-04-05 11:50:12
Message-ID: 202604051143.f5x6elmc7iut@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2026-Apr-05, Antonin Houska wrote:

> ok, maybe just skip the whole cleanup in that special case.

Hmm, should we make this test only in the db_specific case? Doing it
unconditionally makes me a bit nervous (maybe because I don't fully
understand historic snapshot building).

Anyway I just pushed the addition of a progress-suppression bit to
index_create() interface. Here's the rest of the series.

--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"Ninguna manada de bestias tiene una voz tan horrible como la humana" (Orual)

Attachment Content-Type Size
v54-0001-Introduce-an-option-to-make-logical-replication-.patch text/x-diff 21.3 KB
v54-0002-Rename-cluster.c-h-repack.c-h.patch text/x-diff 7.8 KB
v54-0003-Add-CONCURRENTLY-option-to-REPACK-command.patch text/x-diff 174.3 KB
v54-0004-Error-out-any-process-that-would-block-at-REPACK.patch text/x-diff 11.8 KB
v54-0005-Reserve-replication-slots-specifically-for-REPAC.patch text/x-diff 27.8 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Lakhin 2026-04-05 12:00:00 Re: pg_plan_advice
Previous Message Michael Paquier 2026-04-05 11:47:30 Re: [PROPOSAL] Termination of Background Workers for ALTER/DROP DATABASE