Horton

Re: REPACK CONCURRENTLY fails on tables with generated columns

Álvaro Herrera <alvherre@kurilemu.de>

View thread View on postgr.es
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-12T10:25:29Z
Lists: pgsql-hackers 
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?

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
"Update: super-fast reaction on the Postgres bugs mailing list. The report
was acknowledged [...], and a fix is under discussion.
The wonders of open-source !"
             https://twitter.com/gunnarmorling/status/1596080409259003906

Commits

  1. REPACK CONCURRENTLY: Initialize the range table more honestly

  2. Fix REPACK CONCURRENTLY for stored generated columns