Re: BUG #19686: Rolling back SET TABLESPACE + INSERT leads to index corruption

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: exclusion(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19686: Rolling back SET TABLESPACE + INSERT leads to index corruption
Date: 2026-09-28 04:13:14
Message-ID: CAH2-WzkpeZnay88CGdBdwiXJNvvC80EgFOgm0S8V3mEGSCVMuA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sun, Sep 27, 2026 at 4:35 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> > The assertion failure is reproduced starting from 0d861bbb7.
>
> Err, Peter?

The problem has nothing to do with nbtree deduplication -- Alexander
recreated the same problem with a GiST index.. It just so happens that
deduplication has assertions that tend to fail when the same TID is
stored multiple times (e.g., due to a recovery problem).

--
Peter Geoghegan

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Ayush Tiwari 2026-09-28 04:44:08 Re: BUG #19723: CREATE INDEX racing with ALTER INDEX ATTACH PARTITION triggers unexpected internal error
Previous Message Andrey Rachitskiy 2026-09-28 04:03:36 Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY