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

From: Melanie Plageman <melanieplageman(at)gmail(dot)com>
To: Thom Brown <thom(at)linux(dot)com>
Cc: PostgreSQL Hackers <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-23 15:06:50
Message-ID: CAAKRu_b1u9SdACeX90QGLX9LHGosB1eJ_ngyoYfk_B8jDK5_yQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Sep 22, 2026 at 8:23 PM Thom Brown <thom(at)linux(dot)com> wrote:
>
> Whilst stress-testing REPACK (CONCURRENTLY) I managed to get it to silently
> throw away committed updates to a TOASTed column. There's no error, and both
> verify_heapam() and bt_index_check() seem to think everything is fine.

Should this be added as an open item? [1]

- Melanie

[1] https://wiki.postgresql.org/wiki/PostgreSQL_19_Open_Items

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Shashishekar Hullahally Anantharamu 2026-09-23 15:07:03 Re: Possible race condition in pg_basebackup
Previous Message Jonathan S. Katz 2026-09-23 14:51:31 Re: add list of major features to the v19 release notes