Feedback-ID: ia2694551:Fastmail
Date: Wed, 17 Jun 2026 20:19:20 +0200
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Mihail Nikalayeu <mihailnikalayeu@gmail.com>
Cc: Amit Kapila <amit.kapila16@gmail.com>, Antonin Houska <ah@cybertec.at>,
	Andres Freund <andres@anarazel.de>,
 Srinath Reddy Sadipiralla <srinath2133@gmail.com>,
	Matthias van de Meent <boekewurm+postgres@gmail.com>,
 Pg Hackers <pgsql-hackers@lists.postgresql.org>,
	Robert Treat <rob@xzilla.net>
Subject: Re: Adding REPACK [concurrently]
Message-ID: <ajLfxNPl1zg5H--m@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <CADzfLwUeNBCso3e5+d+6CxgcxZ5CJoztLhukvKxmh2rKt7zTDg@mail.gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/ajLfxNPl1zg5H--m%40alvherre.pgsql>
Precedence: bulk

Hello Mihail,

On 2026-Jun-03, Mihail Nikalayeu wrote:

> Hello, everyone!
> 
> I think it is a good time to remind we still have a potential deadlock
> issue leading to loosing vast amount of REPACK work.
> 
> Best soltuion I was able to craft so far is [1].

> [1]: https://www.postgresql.org/message-id/flat/CADzfLwXbUWuS6H4uJEFVL1jS1kzsVnuJ%2BzX1%2BtAEhQxBnEiGKw%40mail.gmail.com

Right.  I spent some time looking at this patch just before pgconf.dev,
and I have to admit I was a bit scared -- that code is really
non-obvious, and breakage here could mean big trouble in case something
goes wrong in weird situations.

So I think we should let this slip for pg19, and get this patch reviewed
and pushed early in pg20 in the coming weeks, so that we have more of a
chance to discover breakage in the time until pg20 release next year.

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
"Por suerte hoy explotó el califont porque si no me habría muerto
 de aburrido"  (Papelucho)