Re: BUG #18490: Assert in comparetup_index_btree_tiebreak() fails when pg_class reindexed during a table creation

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: exclusion(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18490: Assert in comparetup_index_btree_tiebreak() fails when pg_class reindexed during a table creation
Date: 2024-06-02 15:19:19
Message-ID: CAH2-WzkaOCUV_0JYmbv=ZKH5cs6X27eKZLouWq0d6_meGyNJtg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sun, Jun 2, 2024 at 10:57 AM PG Bug reporting form
<noreply(at)postgresql(dot)org> wrote:
> With debug logging added, I confirmed that on a higher lever, inside
> btbuild(), buildstate.spool->sortstate->memtuples really contains two
> tuples pointing to blkno 0, offset 3 after the _bt_spools_heapscan() call.
>
> Reproduced on REL_10_STABLE .. master.

This is a known issue:

https://www.postgresql.org/message-id/CAH2-WzkjjCoq5Y4LeeHJcjYJVxGm3M3SAWZ0%3D6J8K1FPSC9K0w%40mail.gmail.com

(We really should have a bug tracker to track older known bugs such as this.)

--
Peter Geoghegan

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Mor Lehr 2024-06-02 15:26:41 Re: Missing semicolumn in anonymous plpgsql block does not raise syntax error
Previous Message David G. Johnston 2024-06-02 15:19:12 Re: Missing semicolumn in anonymous plpgsql block does not raise syntax error