Re: Adding REPACK [concurrently] - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Adding REPACK [concurrently]
Date
Msg-id 202603311934.ftqj7ytm362y@alvherre.pgsql
Whole thread Raw
In response to Re: Adding REPACK [concurrently]  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-hackers
On 2026-Mar-31, Alvaro Herrera wrote:

> My intention as to patches for final commit is:
> 
> - 0001 "Make index_concurrently_create_copy more general" same as here.
> - 0002 "give options bitmask to table_delete/table_update" same as here,
>        with a real commit message.
> - 0003 Rename cluster.c/h to repack.c/h (similar to 0006 here); no
>        essential change in contents.
> - 0004 "Add CONCURRENTLY option to REPACK command".  Squash of 0003,
>        0004, 0005 and 0007.
> - 0005 "Error out any process that would block at REPACK", same as here.

Here it is with that structure.  The first three should be pretty much
in final form (0003 needs a commit message), but I still want to make
some more cosmetic adjustments to 0004.

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
Thou shalt check the array bounds of all strings (indeed, all arrays), for
surely where thou typest "foo" someone someday shall type
"supercalifragilisticexpialidocious" (5th Commandment for C programmers)

Attachment

pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: Initial COPY of Logical Replication is too slow
Next
From: Andrew Dunstan
Date:
Subject: Re: pg_get__*_ddl consolidation