pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Mihail Nikalayeu <mihailnikalayeu@gmail.com>
Cc: Amit Kapila <amit.kapila16@gmail.com>
Cc: Antonin Houska <ah@cybertec.at>
Cc: Andres Freund <andres@anarazel.de>
Cc: Srinath Reddy Sadipiralla <srinath2133@gmail.com>
Cc: Matthias van de Meent <boekewurm+postgres@gmail.com>
Cc: Pg Hackers <pgsql-hackers@lists.postgresql.org>
Cc: Robert Treat <rob@xzilla.net>
Subject: Re: Adding REPACK [concurrently]
Date: Wed, 17 Jun 2026 20:19:20 +0200
Message-ID: <ajLfxNPl1zg5H--m@alvherre.pgsql> (raw)
In-Reply-To: <CADzfLwUeNBCso3e5+d+6CxgcxZ5CJoztLhukvKxmh2rKt7zTDg@mail.gmail.com>

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%4...

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)





view thread (415+ messages)  latest in thread

Message-ID: <ajLfxNPl1zg5H--m@alvherre.pgsql>
Permalink:  ../ajLfxNPl1zg5H--m@alvherre.pgsql/
Also on:    postgresql.org/message-id/ajLfxNPl1zg5H--m@alvherre.pgsql

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: alvherre@alvh.no-ip.org, mihailnikalayeu@gmail.com, amit.kapila16@gmail.com, ah@cybertec.at, andres@anarazel.de, srinath2133@gmail.com, boekewurm+postgres@gmail.com, pgsql-hackers@lists.postgresql.org, rob@xzilla.net
  Subject: Re: Adding REPACK [concurrently]
  In-Reply-To: <ajLfxNPl1zg5H--m@alvherre.pgsql>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox