Request a Demo
Home   >   mailing lists

Re: REPACK (CONCURRENTLY) might keep dropped-column data - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: REPACK (CONCURRENTLY) might keep dropped-column data
Date
Msg-id asYKAiIp7bUdvrir@alvherre.pgsql
Whole thread
In response to Re: REPACK (CONCURRENTLY) might keep dropped-column data  (shihao zhong <zhong950419@gmail.com>)
Responses Re: REPACK (CONCURRENTLY) might keep dropped-column data
List pgsql-hackers
Tree view 
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/

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Compression of bigger WAL records
Next
From: Michael Banck
Date:
Subject: Low frequency AIO checksum corruption on buildfarm member fruitcrow / GNU Hurd