Re: REPACK (CONCURRENTLY): do not block the table while waiting for the final lock

From: Alvaro Herrera <alvherre(at)kurilemu(dot)de>
To: Antonin Houska <ah(at)cybertec(dot)at>
Cc: shihao zhong <zhong950419(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: REPACK (CONCURRENTLY): do not block the table while waiting for the final lock
Date: 2026-10-06 20:08:28
Message-ID: asVUr6b96xe8oc54@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2026-Oct-06, Antonin Houska wrote:

> shihao zhong <zhong950419(at)gmail(dot)com> wrote:
>
> > Subject: REPACK (CONCURRENTLY): do not block the table while waiting for the final lock
>
> [ I assume this is not meant for v19, is it? ]

I definitely dont't want to change this behavior in 19. At the most,
lets document any shortcomings that the current behavior may have.

For that reason, I don't have any intentions on studying any of these
ideas until we're out of the woods for 19, so to speak :-) -- and out of
2026 TBH.

--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2026-10-06 20:15:15 Re: Show effective xmin in pg_replication_slots when xmin is not set
Previous Message Alvaro Herrera 2026-10-06 20:05:42 Re: REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes