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

From Thom Brown
Subject Re: REPACK (CONCURRENTLY) can silently lose updates when the toast table is rewritten
Date
Msg-id CAA-aLv6JWPo=a7K5kF2UL75hTCQBzktnpZtX+yA5sR9jm-Fh2w@mail.gmail.com
Whole thread
In response to Re: REPACK (CONCURRENTLY) can silently lose updates when the toast table is rewritten  (Melanie Plageman <melanieplageman@gmail.com>)
List pgsql-hackers
On Wed, 23 Sept 2026 at 16:07, Melanie Plageman
<melanieplageman@gmail.com> wrote:
>
> 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]

Yes. I've now added it.

Thanks.

Thom



pgsql-hackers by date:

Previous
From: Nikolay Samokhvalov
Date:
Subject: Re: xact_rollback spikes when logical walsender exits
Next
From: Sehrope Sarkuni
Date:
Subject: Re: Speed up lpad() and rpad() for one-byte padding strings