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 asEEA-lMrIQpGZMN@alvherre.pgsql
Whole thread
In response to Re: REPACK (CONCURRENTLY) might keep dropped-column data  (Antonin Houska <ah@cybertec.at>)
List pgsql-hackers
On 2026-Sep-30, Antonin Houska wrote:

> Álvaro Herrera <alvherre@kurilemu.de> wrote:

> > The adjust_toast_pointers() function should perhaps be renamed,
> > and the comment rewritten, since it's no longer just about toast ...
> > I didn't do that though.
> 
> Maybe prepare_concurrent_update(), as it's called right before
> apply_concurrent_update()?

Thanks, I used this name.

> BTW, I've noticed now that the 'relation' argument of adjust_toast_pointers()
> isn't used anymore. Perhaps it was used before the tuple slots have been
> introduced into the function.

Good catch.  Removed.  Yes, it was used in 0005 with v36 you submitted
[1], but it disappeared when I posted v43 [2], which is when I rewrote
it to use tuple slots.

[1] https://www.postgresql.org/message-id/87648.1772217509@localhost
[2] https://www.postgresql.org/message-id/202603191855.fzsgsnyzfvpt@alvherre.pgsql

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/
"El número de instalaciones de UNIX se ha elevado a 10,
y se espera que este número aumente" (UPM, 1972)



pgsql-hackers by date:

Previous
From: Etsuro Fujita
Date:
Subject: Re: postgres_fdw: transaction mode inheritance corner cases
Next
From: Andrew Dunstan
Date:
Subject: Re: gist_trgm_ops '=' operator: planner picks it over btree, ~300x slower