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

From: Thom Brown <thom(at)linux(dot)com>
To: Melanie Plageman <melanieplageman(at)gmail(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 17:09:08
Message-ID: CAA-aLv6JWPo=a7K5kF2UL75hTCQBzktnpZtX+yA5sR9jm-Fh2w@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 23 Sept 2026 at 16:07, Melanie Plageman
<melanieplageman(at)gmail(dot)com> wrote:
>
> 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]

Yes. I've now added it.

Thanks.

Thom

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Sehrope Sarkuni 2026-09-23 17:16:45 Re: Speed up lpad() and rpad() for one-byte padding strings
Previous Message Nikolay Samokhvalov 2026-09-23 16:43:43 Re: xact_rollback spikes when logical walsender exits