Re: REPACK CONCURRENTLY fails on tables with generated columns
Antonin Houska <ah@cybertec.at>
From: Antonin Houska <ah@cybertec.at>
To: Alvaro Herrera <alvherre@kurilemu.de>
Cc: Ewan Young <kdbase.hack@gmail.com>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
mihailnikalayeu@gmail.com
Date: 2026-06-12T11:01:04Z
Lists: pgsql-hackers
Alvaro Herrera <alvherre@kurilemu.de> wrote: > On 2026-Jun-12, Antonin Houska wrote: > > > I confirm I can reproduce it. I'll post a fix next week. > > Didn't you like Ewan's proposed patch? 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. -- Antonin Houska Web: https://www.cybertec-postgresql.com
Commits
-
REPACK CONCURRENTLY: Initialize the range table more honestly
- 5ee9d7c299f2 master landed
- 5e450df50dc8 19 (unreleased) landed
-
Fix REPACK CONCURRENTLY for stored generated columns
- fb284f2f9bdb 19 (unreleased) landed
- 3be823486f2c master landed