Re: REPACK (CONCURRENTLY) can silently lose updates when the toast table is rewritten

From: shihao zhong <zhong950419(at)gmail(dot)com>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Cc: Álvaro Herrera <alvherre(at)kurilemu(dot)de>, Thom Brown <thom(at)linux(dot)com>, Antonin Houska <ah(at)cybertec(dot)at>, Robert Treat <rob(at)xzilla(dot)net>, Manu <manuelreyesbravo(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: REPACK (CONCURRENTLY) can silently lose updates when the toast table is rewritten
Date: 2026-09-25 18:10:09
Message-ID: CAGRkXqRkybKtWgCqioPthbqtVDU+yVazOHUBDZ-G0ZEy6k6b1A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Done in v5. 0001 is Álvaro's version as one commit, with that comment
added and a shorter commit message. 0002 fixes the decoding_ctx comment
in copy_table_data().

Thanks,
Shihao

Attachment Content-Type Size
v5-0002-Fix-stale-comment-of-copy_table_data.patch application/octet-stream 1.1 KB
v5-0001-Lock-the-TOAST-table-early-in-REPACK-CONCURRENTLY.patch application/octet-stream 10.3 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dirkjan Bussink 2026-09-25 18:27:56 Re: Server crash when describing a FETCH statement after its cursor is closed
Previous Message Tom Lane 2026-09-25 17:58:17 Cleaning up pgcrypto/crypt-des.c to avoid compiler warnings