Re: REPACK CONCURRENTLY fails on tables with generated columns

Álvaro Herrera <alvherre@kurilemu.de>

From: Alvaro Herrera <alvherre@kurilemu.de>
To: Antonin Houska <ah@cybertec.at>
Cc: Ewan Young <kdbase.hack@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, mihailnikalayeu@gmail.com
Date: 2026-06-12T11:40:30Z
Lists: pgsql-hackers
Hello,

On 2026-Jun-12, Antonin Houska wrote:

> After having read the email, I thought that the attachment only contains the
> reproducing test. Now that I look into it, I see it also contains a fix. Sorry
> for the confusion.
> 
> I cannot concentrate on it today, so if I'm supposed to review it, I need a
> few days.

I would welcome your review, but it's not strictly mandatory.  That
said, we have some weeks before the next beta, so there's no rush.

-- 
Álvaro Herrera               48°01'N 7°57'E  —  https://www.EnterpriseDB.com/
"After a quick R of TFM, all I can say is HOLY CR** THAT IS COOL! PostgreSQL was
amazing when I first started using it at 7.2, and I'm continually astounded by
learning new features and techniques made available by the continuing work of
the development team."
Berend Tober, http://archives.postgresql.org/pgsql-hackers/2007-08/msg01009.php



Commits

  1. REPACK CONCURRENTLY: Initialize the range table more honestly

  2. Fix REPACK CONCURRENTLY for stored generated columns