Re: BUG #18396: Assert in gistFindCorrectParent() fails on inserting large tuples into gist index

From: Alexander Lakhin <exclusion(at)gmail(dot)com>
To: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Tender Wang <tndrwang(at)gmail(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18396: Assert in gistFindCorrectParent() fails on inserting large tuples into gist index
Date: 2025-04-04 20:00:01
Message-ID: 7e61e7b5-c887-45d7-a993-9cf4c0b1c2d0@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hello Heikki and Tender Wang,

04.04.2025 14:04, Heikki Linnakangas wrote:
> On 15/11/2024 11:10, Tender Wang wrote:
>>
>> I agree that it doesn't matter. If internal page split due to adjust key consistent with the key we're inserting.
>> The 'retry_from_parent' flag can help us get corrent downlinkoffnum.
>
> Ok, thanks for checking! Committed.
>

Thank you for working on this!

Best regards.
Alexander

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Kirill Reshke 2025-04-04 21:26:29 Re: BUG #18877: PostgreSQL triggers assertion failure
Previous Message PG Bug reporting form 2025-04-04 19:33:44 BUG #18879: PostgreSQL returns memory error.