Re: Adding REPACK [concurrently]

From: Antonin Houska <ah(at)cybertec(dot)at>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Mihail Nikalayeu <mihailnikalayeu(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Robert Treat <rob(at)xzilla(dot)net>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Adding REPACK [concurrently]
Date: 2025-08-15 12:32:09
Message-ID: 76312.1755261129@localhost
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Antonin Houska <ah(at)cybertec(dot)at> wrote:

> Mihail Nikalayeu <mihailnikalayeu(at)gmail(dot)com> wrote:
>
> > One more thing - I think build_new_indexes and
> > index_concurrently_create_copy are very close in semantics, so it
> > might be a good idea to refactor them a bit.
>
> You're right. I think I even used the latter for reference when writing the
> first.
>
> 0002 in the attached series tries to fix that. build_new_indexes() (in 0004)
> is simpler now.

This is v18 again. Parts 0001 through 0004 are unchanged, however 0005 is
added. It implements a new client application pg_repackdb. (If I posted 0005
alone its regression tests would not work. I wonder if the cfbot handles the
repeated occurence of the 'v18-' prefix correctly.)

--
Antonin Houska
Web: https://www.cybertec-postgresql.com

Attachment Content-Type Size
v18-0001-Add-REPACK-command.patch text/x-diff 95.8 KB
v18-0002-Refactor-index_concurrently_create_copy-for-use-with.patch text/x-diff 4.1 KB
v18-0003-Move-conversion-of-a-historic-to-MVCC-snapshot-to-a-.patch text/x-diff 5.4 KB
v18-0004-Add-CONCURRENTLY-option-to-REPACK-command.patch text/plain 147.1 KB
v18-0005-Introduce-repackdb-client-application.patch text/x-diff 97.8 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2025-08-15 12:48:17 Re: Adding REPACK [concurrently]
Previous Message Hayato Kuroda (Fujitsu) 2025-08-15 12:07:30 RE: memory leak in logical WAL sender with pgoutput's cachectx