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

From shihao zhong
Subject Re: REPACK (CONCURRENTLY) might keep dropped-column data
Date
Msg-id CAGRkXqQ7c2v2rQT58GXyuWf_dHJhfOKgK=qy1LDJcAFfjFhAtg@mail.gmail.com
Whole thread
In response to Re: REPACK (CONCURRENTLY) might keep dropped-column data  (Alvaro Herrera <alvherre@kurilemu.de>)
List 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

pgsql-hackers by date:

Previous
From: David Geier
Date:
Subject: Use mbsnrtowcs() in char2wchar() to avoid temporary string copies
Next
From: Nazir Bilal Yavuz
Date:
Subject: Adding init-po and update-po targets to the meson build system