Re: BUG #19686: Rolling back SET TABLESPACE + INSERT leads to index corruption - Mailing list pgsql-bugs

From Peter Geoghegan
Subject Re: BUG #19686: Rolling back SET TABLESPACE + INSERT leads to index corruption
Date
Msg-id CAH2-WzkpeZnay88CGdBdwiXJNvvC80EgFOgm0S8V3mEGSCVMuA@mail.gmail.com
Whole thread
In response to Re: BUG #19686: Rolling back SET TABLESPACE + INSERT leads to index corruption  (Michael Paquier <michael@paquier.xyz>)
List pgsql-bugs
On Sun, Sep 27, 2026 at 4:35 PM Michael Paquier <michael@paquier.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



pgsql-bugs by date:

Previous
From: Andrey Rachitskiy
Date:
Subject: Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY
Next
From: Ayush Tiwari
Date:
Subject: Re: BUG #19723: CREATE INDEX racing with ALTER INDEX ATTACH PARTITION triggers unexpected internal error