Re: REPACK (CONCURRENTLY) might keep dropped-column data

From: Alvaro Herrera <alvherre(at)kurilemu(dot)de>
To: shihao zhong <zhong950419(at)gmail(dot)com>
Cc: Antonin Houska <ah(at)cybertec(dot)at>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Radim Marek <radim(at)boringsql(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: REPACK (CONCURRENTLY) might keep dropped-column data
Date: 2026-10-07 09:02:05
Message-ID: asYKAiIp7bUdvrir@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2026-Oct-06, shihao zhong wrote:

> v2 clears the columns only when replaying an INSERT. restore_tuple()
> and prepare_concurrent_update() stay as they are.

Hm, I just committed v1 with some trivial changes. I don't understand
what does v2 achieve. Are you trying to save having to scan the
attribute array for tuples in DELETE?

--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Banck 2026-10-07 09:15:37 Low frequency AIO checksum corruption on buildfarm member fruitcrow / GNU Hurd
Previous Message Michael Paquier 2026-10-07 08:46:22 Re: Compression of bigger WAL records