Re: BUG #17197: Assert failed on inserting index tuples after VACUUM - Mailing list pgsql-bugs

From Alexander Lakhin
Subject Re: BUG #17197: Assert failed on inserting index tuples after VACUUM
Date
Msg-id f76a292c-9170-1aef-91a0-59d9443b99a3@gmail.com
Whole thread Raw
In response to Re: BUG #17197: Assert failed on inserting index tuples after VACUUM  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: BUG #17197: Assert failed on inserting index tuples after VACUUM  (Peter Geoghegan <pg@bowt.ie>)
List pgsql-bugs
Hello Peter,

21.09.2021 00:03, Peter Geoghegan wrote:
> On Mon, Sep 20, 2021 at 1:35 PM Peter Geoghegan <pg@bowt.ie> wrote:
> Before commit 3c3b8a4b our failing offset number would have at least
> found an LP_UNUSED item -- so no assertion failure. After that commit
> the offset's line pointer might actually be positioned "past the end
> of the line pointer array". But that is a valid state for a heap
> page/HOT chain to have -- so the assertion has it wrong.
>
> I'll push a fix soon. Thanks for the report!
Thanks for the fix!
But if that is a valid (or sane) state, then shouldn't the comment "Some
sanity checks" be removed (or updated) too?

Best regards,
Alexander




pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #17198: Planning time too high when execute query on standby cluster
Next
From: Puneet Sharma
Date:
Subject: Re: BUG #17189: Index not created when primary key created