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

From: shihao zhong <zhong950419(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)kurilemu(dot)de>
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 15:26:51
Message-ID: CAGRkXqQ7c2v2rQT58GXyuWf_dHJhfOKgK=qy1LDJcAFfjFhAtg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Alvaro,

Thanks for committing it.

> Are you trying to save having to scan the attribute array for tuples
> in DELETE?

Yes. Antonin asked if the clearing is needed for DELETE. It is not,
since the old tuple is only used to find the row. But the loop is
cheap, and one place for all changes is simpler. So I withdraw v2.

Thanks,
Shihao

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nazir Bilal Yavuz 2026-10-07 15:35:18 Adding init-po and update-po targets to the meson build system
Previous Message David Geier 2026-10-07 15:01:00 Use mbsnrtowcs() in char2wchar() to avoid temporary string copies