Request a Demo
Home   >   mailing lists

Re: REPACK (CONCURRENTLY) can silently lose updates when the toast table is rewritten - Mailing list pgsql-hackers

From Melanie Plageman
Subject Re: REPACK (CONCURRENTLY) can silently lose updates when the toast table is rewritten
Date
Msg-id CAAKRu_b1u9SdACeX90QGLX9LHGosB1eJ_ngyoYfk_B8jDK5_yQ@mail.gmail.com
Whole thread
In response to REPACK (CONCURRENTLY) can silently lose updates when the toast table is rewritten  (Thom Brown <thom@linux.com>)
Responses Re: REPACK (CONCURRENTLY) can silently lose updates when the toast table is rewritten
List pgsql-hackers
Tree view 
On Tue, Sep 22, 2026 at 8:23 PM Thom Brown <thom@linux.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

pgsql-hackers by date:

Previous
From: "Jonathan S. Katz"
Date:
Subject: Re: add list of major features to the v19 release notes
Next
From: Shashishekar Hullahally Anantharamu
Date:
Subject: Re: Possible race condition in pg_basebackup