Re: REPACK (CONCURRENTLY): do not block the table while waiting for the final lock - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: REPACK (CONCURRENTLY): do not block the table while waiting for the final lock
Date
Msg-id asVUr6b96xe8oc54@alvherre.pgsql
Whole thread
In response to Re: REPACK (CONCURRENTLY): do not block the table while waiting for the final lock  (Antonin Houska <ah@cybertec.at>)
Responses Re: REPACK (CONCURRENTLY): do not block the table while waiting for the final lock
List pgsql-hackers
On 2026-Oct-06, Antonin Houska wrote:

> shihao zhong <zhong950419@gmail.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/



pgsql-hackers by date:

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